qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Chenyi Qiang <chenyi.qiang@intel.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Robert Hoo <robert.hu@linux.intel.com>,
	qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v5 1/4] target/i386: add missing vmx features for several CPU models
Date: Mon, 13 Jul 2020 15:45:55 +0800	[thread overview]
Message-ID: <b67d7f1c-4a1f-dc57-ceb5-70dd8da9b5d8@intel.com> (raw)
In-Reply-To: <7b8ceab5-2bf4-0905-ff9f-b2d9e2bd89a1@intel.com>

On 7/13/2020 3:23 PM, Chenyi Qiang wrote:
> 
> 
> On 7/11/2020 12:48 AM, Eduardo Habkost wrote:
>> On Fri, Jul 10, 2020 at 09:45:49AM +0800, Chenyi Qiang wrote:
>>>
>>>
>>> On 7/10/2020 6:12 AM, Eduardo Habkost wrote:
>>>>
>>>> I'm very sorry for taking so long to review this.  Question
>>>> below:
>>>>
>>>> On Fri, Jun 19, 2020 at 03:31:11PM +0800, Chenyi Qiang wrote:
>>>>> Add some missing VMX features in Skylake-Server, Cascadelake-Server 
>>>>> and
>>>>> Icelake-Server CPU models based on the output of Paolo's script.
>>>>>
>>>>> Signed-off-by: Chenyi Qiang <chenyi.qiang@intel.com>
>>>>
>>>> Why are you changing the v1 definition instead adding those new
>>>> features in a new version of the CPU model, just like you did in
>>>> patch 3/4?
>>>>
>>>
>>> I suppose these missing vmx features are not quite necessary for 
>>> customers.
>>> Just post it here to see if they are worth being added.
>>> Adding a new version is reasonable. Is it appropriate to put all the 
>>> missing
>>> features in patch 1/4, 3/4, 4/4 in a same version?
>>
>> Yes, it would be OK to add only one new version with all the new
>> features.
>>
> 
> During the coding, I prefer to split the missing vmx features into a new 
> version of CPU model, because the vmx features depends on CPUID_EXT_VMX. 
> I think It would be better to distinguish it instead of enabling the vmx 
> transparently. i.e.
> {
>      .version = 4,
>      .props = (PropValue[]) {
>          { "sha-ni", "on" },
>          ... ...
>          { "model", "106" },
>                  { /* end of list */ }
>      },
> },
> {
>      .version = 5,
>      .props = (PropValue[]) {
>          { "vmx", "on" }

Chenyi,

This is not we have discussed. I prefer to changing the logic of 
versioned CPU model to not add the features in versioned CPU model to 
env->user_features[]. They're not supposed to be added to 
env->user_features[] since they're not set by user through -feature/+feature

Eduardo,

What do you think?



  reply	other threads:[~2020-07-13  7:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19  7:31 [PATCH v5 0/4] modify CPU model info Chenyi Qiang
2020-06-19  7:31 ` [PATCH v5 1/4] target/i386: add missing vmx features for several CPU models Chenyi Qiang
2020-07-09 22:12   ` Eduardo Habkost
2020-07-10  1:45     ` Chenyi Qiang
2020-07-10 16:48       ` Eduardo Habkost
2020-07-11  2:00         ` Chenyi Qiang
2020-07-13  7:23         ` Chenyi Qiang
2020-07-13  7:45           ` Xiaoyao Li [this message]
2020-07-13 14:44             ` Eduardo Habkost
2020-07-13 15:07               ` Xiaoyao Li
2020-07-13 16:35                 ` Eduardo Habkost
2020-06-19  7:31 ` [PATCH v5 2/4] target/i386: add fast short REP MOV support Chenyi Qiang
2020-07-09 22:22   ` Eduardo Habkost
2020-06-19  7:31 ` [PATCH v5 3/4] target/i386: add the missing features for Icelake-Server CPU model Chenyi Qiang
2020-07-09 22:22   ` Eduardo Habkost
2020-06-19  7:31 ` [PATCH v5 4/4] target/i386: modify Icelake-Server CPU model number Chenyi Qiang
2020-07-09 22:12   ` Eduardo Habkost
2020-06-19  7:55 ` [PATCH v5 0/4] modify CPU model info no-reply

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=b67d7f1c-4a1f-dc57-ceb5-70dd8da9b5d8@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=chenyi.qiang@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.hu@linux.intel.com \
    --cc=rth@twiddle.net \
    /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).