[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 4/6] x86/Intel: use host CPU policy for ARAT checking
- To: Jan Beulich <jbeulich@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Jason Andryuk <jason.andryuk@xxxxxxx>
- Date: Tue, 9 Dec 2025 17:30:24 -0500
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=suse.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=IOSKOhB9Uh50SUCYA9S45RoHyTm6kIqe2zEweHtRT8Y=; b=iSTbVxV7BVupTdgWWzo/NDxR8yi3Kc9xL2GxTbSTQHB0hFrZ5CYIDwkxJeP/xCcw6UQ0mTiox4N2G+HqpBxnS3GDpmXjAJblivqZRsd3XdEhSro5nAhAkDlGKluauBeoxVuIAl066TJo7SBU+fWIye9UchsoCEShhoqUbpvf5hd34Wb4aiApTmYPVRwkUpQenYrQ35amDnT2T0WWTNWq1dgDiIiWQCh7ij+6BnMnuc+EnhwiH1DrqIN4tYnnkAMnvUnnUEQwmHfEcQir8K+4zidzohF5eTLZ7zYv4BGobBNneFTs13V6l2py+lSWoUGaSi5OaNFhRQpu4ELztgiyjQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=RYD7E7iE+BoZNY6NdkW0V7UUkdUxu3LMQkVTcOGyeCAtQfZodR5XnImmXAFMx8Zd/7TXrLGgwj73lcCeO6o9w7z0h37oW4EI5eVdyyUrfHEYMlGdNYKQihLwf6SKsJH/5l28DEBuYdyYlbR3RoyoYGbzEBRz9O9+rZHflSIy2ud0AdUnAZzsokjrhsgAfuMhyNkrnFJrXMw6PGiOevieaJPGHfVdqNV2FxYuard2LAEcuUcoefa/n5blSjGXmQR9uB8IRSs2HL8DTby5hv0Si5eUwdfBMpJjO7QMV+NT8Urj21AIFg+e26qHhMetJgJT8FGhfaA1fcYd169cYXzobw==
- Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Delivery-date: Tue, 09 Dec 2025 22:30:44 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 2025-11-24 07:24, Jan Beulich wrote:
There's no need to invoke CPUID yet another time. However, as the host CPU
policy is set up only shortly after init_intel() ran on the BSP, defer the
logic to a pre-SMP initcall. This can't be (a new) one in cpu/intel.c
though, as that's linked after acpi/cpu_idle.c (which is where we already
need the feature set). Since opt_arat is local to the cpu/ subtree,
introduce a new Intel-specific helper to hold the code needed.
Further, as we assume symmetry anyway, use setup_force_cpu_cap() and hence
limit the checking to the boot CPU.
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
Reviewed-by: Jason Andryuk <jason.andryuk@xxxxxxx>
|
