From: "H. Peter Anvin" <hpa@zytor.com>
To: Sean Christopherson <seanjc@google.com>, Arnd Bergmann <arnd@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Arnd Bergmann <arnd@arndb.de>,
kernel test robot <lkp@intel.com>,
Michael Roth <michael.roth@amd.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: kvm: add back X86_LOCAL_APIC dependency
Date: Tue, 12 Nov 2024 10:10:14 -0800 [thread overview]
Message-ID: <8c70586e-2513-42d4-b2cd-476caa416c16@zytor.com> (raw)
In-Reply-To: <ZzOY-AlBgouiIbDB@google.com>
On 11/12/24 10:05, Sean Christopherson wrote:
>>
>> Fixes: ea4290d77bda ("KVM: x86: leave kvm.ko out of the build if no vendor module is requested")
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202410060426.e9Xsnkvi-lkp@intel.com/
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> ---
>> Question: is there actually any point in keeping KVM support for 32-bit host
>> processors?
>
> Nope. We need _a_ 32-bit KVM build to run as a nested (L1) hypervisor for testing
> purposes, but AFAIK there's zero need to keep 32-bit KVM up-to-date.
>
What do you mean here? Running an old kernel with the 32-bit KVM in a VM
for testing the L0 hypervisor?
-hpa
next prev parent reply other threads:[~2024-11-12 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 6:53 Arnd Bergmann
2024-11-12 18:05 ` Sean Christopherson
2024-11-12 18:10 ` H. Peter Anvin [this message]
2024-11-12 18:22 ` Sean Christopherson
2024-11-13 14:42 ` Sean Christopherson
2024-11-13 15:54 ` Arnd Bergmann
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=8c70586e-2513-42d4-b2cd-476caa416c16@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®