archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: Thomas Gleixner <>
Cc: Ingo Molnar <>, "H . Peter Anvin" <>,, Greg Kroah-Hartman <>,,
	Linus Torvalds <>,
	Guenter Roeck <>, Meelis Roos <>,
	Paolo Bonzini <>
Subject: [PATCH RESEND] x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is disabled
Date: Wed, 15 Aug 2018 08:38:33 -0700	[thread overview]
Message-ID: <> (raw)

allmodconfig+CONFIG_INTEL_KVM=n results in the following build error.

ERROR: "l1tf_vmx_mitigation" [arch/x86/kvm/kvm.ko] undefined!

Fixes: 5b76a3cff011 ("KVM: VMX: Tell the nested hypervisor to skip L1D flush on vmentry")
Reported-by: Meelis Roos <>
Cc: Meelis Roos <>
Cc: Paolo Bonzini <>
Cc: Thomas Gleixner <>
Signed-off-by: Guenter Roeck <>
Sorry for the early resend; widening the audience.

This problem affects Chrome OS builds, and I'll need to apply either
this or a similar patch.
Since I would like to avoid applying a patch just to revert it later, any
feedback if this is the correct patch or even the right approach would be
most appreciated.


 arch/x86/kernel/cpu/bugs.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
index 27830880e7a7..cb4a16292aa7 100644
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -664,10 +664,9 @@ void x86_spec_ctrl_setup_ap(void)
 enum l1tf_mitigations l1tf_mitigation __ro_after_init = L1TF_MITIGATION_FLUSH;
 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_AUTO;
 static void __init l1tf_select_mitigation(void)

             reply	other threads:[~2018-08-15 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 15:38 Guenter Roeck [this message]
2018-08-15 16:46 ` [PATCH RESEND] x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is disabled Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).