[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3855e044-f2d1-6371-018a-c2d32031d8fb@redhat.com>
Date: Thu, 10 Oct 2019 00:49:27 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Jim Mattson <jmattson@...gle.com>,
Marc Orr <marcorr@...gle.com>, Peter Shier <pshier@...gle.com>,
Jacob Xu <jacobhxu@...gle.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
kvm@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 08/26] kvm: x86: Improve emulation of CPUID
leaves 0BH and 1FH
On 10/10/19 00:41, Sasha Levin wrote:
>> Is it possible for KVM to opt
>> out of this AUTOSEL nonsense?
>
> Sure, I've opted out KVM and removed all KVM patches from this series:
Thanks!
Paolo
> c1fac4516a61d kvm: vmx: Limit guest PMCs to those supported on the host
> 75b118586ec81 kvm: x86, powerpc: do not allow clearing largepages
> debugfs entry
> 06cd1710feaed KVM: VMX: Set VMENTER_L1D_FLUSH_NOT_REQUIRED if !X86_BUG_L1TF
> c89fc5c082aa6 KVM: x86: Expose XSAVEERPTR to the guest
> 1eec6b4068e2e kvm: x86: Use AMD CPUID semantics for AMD vCPUs
> 5c56e6ba0afc8 kvm: x86: Improve emulation of CPUID leaves 0BH and 1FH
> 94a3c6f010bd2 kvm: x86: Fix a spurious -E2BIG in __do_cpuid_func
Powered by blists - more mailing lists