x86/cpu-policy: Simplify logic in guest_common_default_feature_adjustments()

For features which are unconditionally set in the max policies, making the
default policy to match the host can be done with a conditional clear.

This is simpler than the unconditional clear, conditional set currently
performed.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
(cherry picked from commit 30f8fed68f)
This commit is contained in:
Andrew Cooper committed 2025-07-07 22:52:21 +01:00
1 parent b6436bb005
commit 60522d4040
1 file changed
+10 -15
+10 -15
View File
@@ -518,17 +518,14 @@ static void __init guest_common_default_feature_adjustments(uint32_t *fs)
* reasons, so reset the default policy back to the host values in
* case we're unaffected.
*/
__clear_bit(X86_FEATURE_MD_CLEAR, fs);
if ( cpu_has_md_clear )
__set_bit(X86_FEATURE_MD_CLEAR, fs);
if ( !cpu_has_md_clear )
__clear_bit(X86_FEATURE_MD_CLEAR, fs);
__clear_bit(X86_FEATURE_FB_CLEAR, fs);
if ( cpu_has_fb_clear )
__set_bit(X86_FEATURE_FB_CLEAR, fs);
if ( !cpu_has_fb_clear )
__clear_bit(X86_FEATURE_FB_CLEAR, fs);
__clear_bit(X86_FEATURE_RFDS_CLEAR, fs);
if ( cpu_has_rfds_clear )
__set_bit(X86_FEATURE_RFDS_CLEAR, fs);
if ( !cpu_has_rfds_clear )
__clear_bit(X86_FEATURE_RFDS_CLEAR, fs);
/*
* The Gather Data Sampling microcode mitigation (August 2023) has an
@@ -548,13 +545,11 @@ static void __init guest_common_default_feature_adjustments(uint32_t *fs)
* Topology information is at the toolstack's discretion so these are
* unconditionally set in max, but pick a default which matches the host.
*/
__clear_bit(X86_FEATURE_HTT, fs);
if ( cpu_has_htt )
__set_bit(X86_FEATURE_HTT, fs);
if ( !cpu_has_htt )
__clear_bit(X86_FEATURE_HTT, fs);
__clear_bit(X86_FEATURE_CMP_LEGACY, fs);
if ( cpu_has_cmp_legacy )
__set_bit(X86_FEATURE_CMP_LEGACY, fs);
if ( !cpu_has_cmp_legacy )
__clear_bit(X86_FEATURE_CMP_LEGACY, fs);
/*
* On certain hardware, speculative or errata workarounds can result in
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.