x86: correct default_xen_spec_ctrl calculation

Even with opt_msr_sc_{pv,hvm} both false we should set up the variable
as usual, to ensure proper one-time setup during boot and CPU bringup.
This then also brings the code in line with the comment immediately
ahead of the printk() being modified saying "irrespective of guests".

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
master commit: d6239f6471
master date: 2018-05-29 12:38:52 +0200
This commit is contained in:
Jan Beulich committed 2018-07-04 12:26:24 +02:00
1 parent dd07d3e25c
commit 3bd7966eba
1 file changed
+7 -12
+7 -12
View File
@@ -183,8 +183,6 @@ custom_param("spec-ctrl", parse_spec_ctrl);
static void __init print_details(enum ind_thunk thunk, uint64_t caps)
{
bool use_spec_ctrl = (boot_cpu_has(X86_FEATURE_SC_MSR_PV) ||
boot_cpu_has(X86_FEATURE_SC_MSR_HVM));
unsigned int _7d0 = 0, e8b = 0, tmp;
/* Collect diagnostics about available mitigations. */
@@ -216,10 +214,9 @@ static void __init print_details(enum ind_thunk thunk, uint64_t caps)
thunk == THUNK_RETPOLINE ? "RETPOLINE" :
thunk == THUNK_LFENCE ? "LFENCE" :
thunk == THUNK_JMP ? "JMP" : "?",
!use_spec_ctrl ? "No" :
(default_xen_spec_ctrl & SPEC_CTRL_IBRS) ? "IBRS+" : "IBRS-",
!use_spec_ctrl || !boot_cpu_has(X86_FEATURE_SSBD)
? "" :
!boot_cpu_has(X86_FEATURE_IBRSB) ? "No" :
(default_xen_spec_ctrl & SPEC_CTRL_IBRS) ? "IBRS+" : "IBRS-",
!boot_cpu_has(X86_FEATURE_SSBD) ? "" :
(default_xen_spec_ctrl & SPEC_CTRL_SSBD) ? " SSBD+" : " SSBD-",
opt_ibpb ? " IBPB" : "");
@@ -561,16 +558,14 @@ void __init init_speculation_mitigations(void)
}
if ( use_spec_ctrl )
{
if ( ibrs )
default_xen_spec_ctrl |= SPEC_CTRL_IBRS;
default_spec_ctrl_flags |= SCF_ist_wrmsr;
}
if ( ibrs )
default_xen_spec_ctrl |= SPEC_CTRL_IBRS;
}
/* If we have SSBD available, see whether we should use it. */
if ( boot_cpu_has(X86_FEATURE_SSBD) && use_spec_ctrl && opt_ssbd )
if ( boot_cpu_has(X86_FEATURE_SSBD) && opt_ssbd )
default_xen_spec_ctrl |= SPEC_CTRL_SSBD;
/*
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.