From: Tao Xu <tao3.xu@intel.com>
To: "Eric Blake" <eblake@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: ehabkost@redhat.com, xiaoyao.li@intel.com, qemu-devel@nongnu.org,
pbonzini@redhat.com, robert.hu@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2] i386: Add some MSR based features on Cascadelake-Server CPU model
Date: Wed, 8 May 2019 08:54:00 +0800 [thread overview]
Message-ID: <fee742a0-a836-c7aa-37f9-607986a57876@intel.com> (raw)
In-Reply-To: <69089c48-629c-1297-84cf-63877f803802@redhat.com>
On 5/7/2019 11:06 PM, Eric Blake wrote:
> On 5/7/19 8:07 AM, Daniel P. Berrangé wrote:
>> On Tue, May 07, 2019 at 08:48:53PM +0800, Tao Xu wrote:
>>> As noted in
>>> http://lists.gnu.org/archive/html/qemu-devel/2018-09/msg02212.html
>>
>> Rather than pointing to the mailing list post, please just refer
>> to the git commit hash that patch was merged under, which IIUC
>> is c7a88b52f62b30c04158eeb07f73e3f72221b6a8.
>>
>>> Because MSR based feature has been supported by QEMU,
>>> we add CPUID_7_0_EDX_ARCH_CAPABILITIES on Cascadelake-Server CPU
>>> model, and add IA32_ARCH_CAPABILITIES MSR based features (RDCL_NO,
>>> IBRS_ALL and SKIP_L1DFL_VMENTRY).
>>>
>>> And "014018e19b i386: Make arch_capabilities migratable" has been
>>> in QEMU upstream, the CPUID_7_0_EDX_ARCH_CAPABILITIES can be
>>> safely added into CPU Model.
>
> Also, this paragraph:
>
>>>
>>> Changes in v2:
>>> - rebased patch to latest qemu base
>
> is useful to the list reader but not to the permanent git history, so it
> belongs better...
>
>>>
>>> Signed-off-by: Tao Xu <tao3.xu@intel.com>
>>> ---
>
> ...here, after the --- marker, so that 'git am' will strip it on the
> maintainer's behalf when they prepare the patch for a pull request.
>
Thank your for your suggestion, Eric. I will rewrite my commit message.
next prev parent reply other threads:[~2019-05-08 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 12:48 [Qemu-devel] [PATCH v2] i386: Add some MSR based features on Cascadelake-Server CPU model Tao Xu
2019-05-07 13:07 ` Daniel P. Berrangé
2019-05-07 15:06 ` Eric Blake
2019-05-08 0:54 ` Tao Xu [this message]
2019-05-08 0:51 ` Tao Xu
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=fee742a0-a836-c7aa-37f9-607986a57876@intel.com \
--to=tao3.xu@intel.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=rth@twiddle.net \
--cc=xiaoyao.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).