x86: Move SVM features exposed to guest into hvm_max_cpu_policy

Currently (nested) SVM features we're willing to expose to the guest
are defined in calculate_host_policy, and stored in host_cpu_policy.
This is the wrong place for this; move it into
calculate_hvm_max_policy(), and store it in hvm_max_cpu_policy.

Signed-off-by: George Dunlap <george.dunlap@cloud.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
This commit is contained in:
George Dunlap committed 2024-03-27 11:44:52 +00:00
1 parent e3883336bb
commit 4f8b0e94d7
1 file changed
+17 -13
+17 -13
View File
@@ -398,19 +398,6 @@ static void __init calculate_host_policy(void)
if ( vpmu_mode == XENPMU_MODE_OFF )
p->basic.raw[0xa] = EMPTY_LEAF;
if ( p->extd.svm )
{
/* Clamp to implemented features which require hardware support. */
p->extd.raw[0xa].d &= ((1u << SVM_FEATURE_NPT) |
(1u << SVM_FEATURE_LBRV) |
(1u << SVM_FEATURE_NRIPS) |
(1u << SVM_FEATURE_PAUSEFILTER) |
(1u << SVM_FEATURE_DECODEASSISTS));
/* Enable features which are always emulated. */
p->extd.raw[0xa].d |= ((1u << SVM_FEATURE_VMCBCLEAN) |
(1u << SVM_FEATURE_TSCRATEMSR));
}
/* 0x000000ce MSR_INTEL_PLATFORM_INFO */
/* probe_cpuid_faulting() sanity checks presence of MISC_FEATURES_ENABLES */
p->platform_info.cpuid_faulting = cpu_has_cpuid_faulting;
@@ -741,6 +728,23 @@ static void __init calculate_hvm_max_policy(void)
if ( !cpu_has_vmx )
__clear_bit(X86_FEATURE_PKS, fs);
/*
* Make adjustments to possible (nested) virtualization features exposed
* to the guest
*/
if ( p->extd.svm )
{
/* Clamp to implemented features which require hardware support. */
p->extd.raw[0xa].d &= ((1u << SVM_FEATURE_NPT) |
(1u << SVM_FEATURE_LBRV) |
(1u << SVM_FEATURE_NRIPS) |
(1u << SVM_FEATURE_PAUSEFILTER) |
(1u << SVM_FEATURE_DECODEASSISTS));
/* Enable features which are always emulated. */
p->extd.raw[0xa].d |= ((1u << SVM_FEATURE_VMCBCLEAN) |
(1u << SVM_FEATURE_TSCRATEMSR));
}
guest_common_max_feature_adjustments(fs);
guest_common_feature_adjustments(fs);
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.