[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c70586e-2513-42d4-b2cd-476caa416c16@zytor.com>
Date: Tue, 12 Nov 2024 10:10:14 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Sean Christopherson <seanjc@...gle.com>, Arnd Bergmann <arnd@...nel.org>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner
<tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
Arnd Bergmann <arnd@...db.de>, kernel test robot <lkp@...el.com>,
Michael Roth <michael.roth@....com>,
Isaku Yamahata <isaku.yamahata@...el.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: kvm: add back X86_LOCAL_APIC dependency
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@...el.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202410060426.e9Xsnkvi-lkp@intel.com/
>> Signed-off-by: Arnd Bergmann <arnd@...db.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
Powered by blists - more mailing lists