Re: [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest

On 27/01/21 01:57, Chenyi Qiang wrote: What is the status of the patch to introduce X86_FEATURE_BUS_LOCK_DETECT (I saw https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2389369.html)? Paolo Fenghua sent the v4 patch and pinged x86 maintainers, but still no feedback. https://

Re: [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest

On 1/27/2021 12:33 AM, Paolo Bonzini wrote: On 08/01/21 19:16, kernel test robot wrote: Hi Chenyi, Thank you for the patch! Yet something to improve: [auto build test ERROR on kvm/linux-next] [also build test ERROR on v5.11-rc2 next-20210108] [If your patch is applied to the wrong git tree,

Re: [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest

On 08/01/21 19:16, kernel test robot wrote: Hi Chenyi, Thank you for the patch! Yet something to improve: [auto build test ERROR on kvm/linux-next] [also build test ERROR on v5.11-rc2 next-20210108] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patc

Re: [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest

Hi Chenyi, Thank you for the patch! Yet something to improve: [auto build test ERROR on kvm/linux-next] [also build test ERROR on v5.11-rc2 next-20210108] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in

[RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest

Bus lock debug exception is an ability to notify the kernel by an #DB trap after the instruction acquires a bus lock and is executed when CPL>0. This allows the kernel to enforce user application throttling or mitigations. Existence of bus lock debug exception is enumerated via CPUID.(EAX=7,ECX=0)