From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH 0/2] KVM: x86: Fix more KVM_X86 Kconfig bugs
Date: Mon, 18 Nov 2024 09:20:00 -0800 [thread overview]
Message-ID: <20241118172002.1633824-1-seanjc@google.com> (raw)
Fix two more bugs in the KVM_X86 Kconfig. The fix from Arnd resolves a
build failure, but practically speaking is a non-issue because the failure
only affects 32-bit !SMP builds that effectively disable the local APIC.
The second fix is far more urgent. It resolves a bug where KVM's Kconfig
doesn't correctly define KVM_X86, and will build kvm.ko as a module when
KVM=y if neither KVM_INTEL nor KVM_AMD is 'y', e.g. if KVM=y, KVM_INTEL,=m,
and KVM_AMD=m. I don't know if any distros use that combo, but it broke
our production kernel, so it's certainly possible that it broke other
setups too.
Arnd's fix was already posted, but I bundled it here to avoid a trivial
conflict and to ensure it doesn't get left behind.
Arnd Bergmann (1):
KVM: x86: add back X86_LOCAL_APIC dependency
Sean Christopherson (1):
KVM: x86: Break CONFIG_KVM_X86's direct dependency on KVM_INTEL ||
KVM_AMD
arch/x86/kvm/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: adc218676eef25575469234709c2d87185ca223a
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-11-18 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 17:20 Sean Christopherson [this message]
2024-11-18 17:20 ` [PATCH 1/2] KVM: x86: add back X86_LOCAL_APIC dependency Sean Christopherson
2024-11-18 17:20 ` [PATCH 2/2] KVM: x86: Break CONFIG_KVM_X86's direct dependency on KVM_INTEL || KVM_AMD Sean Christopherson
2024-11-20 0:35 ` [PATCH 0/2] KVM: x86: Fix more KVM_X86 Kconfig bugs Paolo Bonzini
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241118172002.1633824-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=arnd@arndb.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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