From: Paolo Bonzini <pbonzini@redhat.com>
To: "Qi, Yadong" <yadong.qi@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: "Christopherson, Sean J" <sean.j.christopherson@intel.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"jmattson@google.com" <jmattson@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>,
"liran.alon@oracle.com" <liran.alon@oracle.com>,
"nikita.leshchenko@oracle.com" <nikita.leshchenko@oracle.com>,
"Gao, Chao" <chao.gao@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Chen, Luhai" <luhai.chen@intel.com>,
"Zhu, Bing" <bing.zhu@intel.com>,
"Wang, Kai Z" <kai.z.wang@intel.com>
Subject: Re: [PATCH] KVM: x86: emulate wait-for-SIPI and SIPI-VMExit
Date: Sun, 27 Sep 2020 08:54:48 +0200 [thread overview]
Message-ID: <5019ebd5-4612-ae15-f976-a95000d0e1ad@redhat.com> (raw)
In-Reply-To: <MWHPR11MB1968CD560E8BB15613F3EA73E3340@MWHPR11MB1968.namprd11.prod.outlook.com>
On 27/09/20 03:51, Qi, Yadong wrote:
>> Subject: RE: [PATCH] KVM: x86: emulate wait-for-SIPI and SIPI-VMExit
>>
>>> Again, this looks good but it needs testcases.
>>
>> Yes, the unit test development is WIP.
>>
>
> Hi, Paolo
>
> I have sent out the unit test patch.
> https://patchwork.kernel.org/patch/11799305/
> Could you help review it? Thanks a lot.
Yes, I've seen it. Tomorrow. :)
Paolo
next prev parent reply other threads:[~2020-09-27 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 5:23 [PATCH] KVM: x86: emulate wait-for-SIPI and SIPI-VMExit yadong.qi
2020-09-22 9:09 ` Paolo Bonzini
2020-09-23 0:42 ` Qi, Yadong
2020-09-27 1:51 ` Qi, Yadong
2020-09-27 6:54 ` Paolo Bonzini [this message]
2020-11-02 5:42 ` Qi, Yadong
2020-11-05 16:08 ` Paolo Bonzini
2020-11-06 6:47 ` Qi, Yadong
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=5019ebd5-4612-ae15-f976-a95000d0e1ad@redhat.com \
--to=pbonzini@redhat.com \
--cc=bing.zhu@intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kai.z.wang@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=luhai.chen@intel.com \
--cc=mingo@redhat.com \
--cc=nikita.leshchenko@oracle.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=yadong.qi@intel.com \
/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.