[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c6e8f32-f831-29f1-b749-d0873dad20eb@linux.intel.com>
Date: Sun, 22 Oct 2023 20:35:48 +0800
From: Binbin Wu <binbin.wu@...ux.intel.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
pbonzini@...hat.com, chao.gao@...el.com, kai.huang@...el.com,
David.Laight@...lab.com, robert.hu@...ux.intel.com,
guang.zeng@...el.com
Subject: Re: [PATCH v11 00/16] LAM and LASS KVM Enabling
On 10/21/2023 8:34 AM, Sean Christopherson wrote:
> On Fri, Oct 20, 2023, Sean Christopherson wrote:
>> On Wed, Sep 13, 2023, Binbin Wu wrote:
>>> Binbin Wu (10):
>>> KVM: x86: Consolidate flags for __linearize()
>>> KVM: x86: Use a new flag for branch targets
>>> KVM: x86: Add an emulation flag for implicit system access
>>> KVM: x86: Add X86EMUL_F_INVLPG and pass it in em_invlpg()
>>> KVM: x86/mmu: Drop non-PA bits when getting GFN for guest's PGD
>>> KVM: x86: Add & use kvm_vcpu_is_legal_cr3() to check CR3's legality
>>> KVM: x86: Remove kvm_vcpu_is_illegal_gpa()
>>> KVM: x86: Introduce get_untagged_addr() in kvm_x86_ops and call it in
>>> emulator
>>> KVM: x86: Untag address for vmexit handlers when LAM applicable
>>> KVM: x86: Use KVM-governed feature framework to track "LAM enabled"
>>>
>>> Robert Hoo (3):
>>> KVM: x86: Virtualize LAM for supervisor pointer
>>> KVM: x86: Virtualize LAM for user pointer
>>> KVM: x86: Advertise and enable LAM (user and supervisor)
>>>
>>> Zeng Guang (3):
>>> KVM: emulator: Add emulation of LASS violation checks on linear
>>> address
>>> KVM: VMX: Virtualize LASS
>>> KVM: x86: Advertise LASS CPUID to user space
>> This all looks good! I have a few minor nits, but nothing I can't tweak when
>> applying. Assuming nothing explodes in testing, I'll get this applied for 6.8
>> next week.
Thanks very much!
> Gah, by "this" I meant the LAM parts. LASS is going to have to wait until the
> kernel support lands.
Powered by blists - more mailing lists