[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c38f1be-47c3-e8f8-ee72-9642e99ac93f@intel.com>
Date: Wed, 27 Jan 2021 08:57:55 +0800
From: Chenyi Qiang <chenyi.qiang@...el.com>
To: Paolo Bonzini <pbonzini@...hat.com>,
kernel test robot <lkp@...el.com>,
Sean Christopherson <seanjc@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
Xiaoyao Li <xiaoyao.li@...el.com>
Cc: kbuild-all@...ts.01.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: 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, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>
> 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://lore.kernel.org/lkml/YA8bkmYjShKwmyXx@otcwcpicx3.sc.intel.com/
>
Powered by blists - more mailing lists