From: Chenyi Qiang <chenyi.qiang@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest
Date: Wed, 27 Jan 2021 08:57:55 +0800 [thread overview]
Message-ID: <3c38f1be-47c3-e8f8-ee72-9642e99ac93f@intel.com> (raw)
In-Reply-To: <cfc345ea-980d-821d-f3a6-cea1f8e7ba03@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
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(a)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(a)otcwcpicx3.sc.intel.com/
>
WARNING: multiple messages have this Message-ID (diff)
From: Chenyi Qiang <chenyi.qiang@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kernel test robot <lkp@intel.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Xiaoyao Li <xiaoyao.li@intel.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest
Date: Wed, 27 Jan 2021 08:57:55 +0800 [thread overview]
Message-ID: <3c38f1be-47c3-e8f8-ee72-9642e99ac93f@intel.com> (raw)
In-Reply-To: <cfc345ea-980d-821d-f3a6-cea1f8e7ba03@redhat.com>
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/
>
next prev parent reply other threads:[~2021-01-27 0:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 6:49 [RESEND PATCH 0/2] Add KVM support for bus lock debug exception Chenyi Qiang
2021-01-08 6:49 ` [RESEND PATCH 1/2] KVM: X86: Add support for the emulation of DR6_BUS_LOCK bit Chenyi Qiang
2021-01-08 16:38 ` kernel test robot
2021-01-08 16:38 ` kernel test robot
2021-01-26 16:31 ` Paolo Bonzini
2021-01-27 1:48 ` Chenyi Qiang
2021-01-27 3:41 ` Xiaoyao Li
2021-01-27 10:04 ` Paolo Bonzini
2021-01-28 7:17 ` Xiaoyao Li
2021-01-28 7:25 ` Paolo Bonzini
2021-01-28 7:41 ` Xiaoyao Li
2021-01-08 6:49 ` [RESEND PATCH 2/2] KVM: X86: Expose bus lock debug exception to guest Chenyi Qiang
2021-01-08 18:16 ` kernel test robot
2021-01-08 18:16 ` kernel test robot
2021-01-26 16:33 ` Paolo Bonzini
2021-01-26 16:33 ` Paolo Bonzini
2021-01-27 0:57 ` Chenyi Qiang [this message]
2021-01-27 0:57 ` Chenyi Qiang
2021-01-27 12:31 ` Paolo Bonzini
2021-01-27 12:31 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c38f1be-47c3-e8f8-ee72-9642e99ac93f@intel.com \
--to=chenyi.qiang@intel.com \
--cc=kbuild-all@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.