qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "haoxudong.hao@gmail.com" <haoxudong.hao@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Gleb Natapov <gleb@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] target-i386: fix cpuid leaf 0x0d
Date: Fri, 29 Nov 2013 16:11:42 +0100	[thread overview]
Message-ID: <5298AEAE.2070908@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC8292335013EF505@SHSMSX101.ccr.corp.intel.com>

Il 29/11/2013 15:46, Liu, Jinsong ha scritto:
> Paolo Bonzini wrote:
>> Il 29/11/2013 14:15, Liu, Jinsong ha scritto:
>>> From e4b58c7bafc4d9f913a572a1b1cfee91c92f1637 Mon Sep 17 00:00:00
>>> 2001 
>>> From: Liu Jinsong <jinsong.liu@intel.com>
>>> Date: Fri, 22 Nov 2013 00:24:16 +0800
>>> Subject: [PATCH 1/2] target-i386: fix cpuid leaf 0x0d
>>>
>>> Fix cpuid leaf 0x0d which incorrectly parsed eax and ebx.
>>
>> There is no visible change right (the two hunks cancel each other)?
>> Since you will have to post a v2, please make this explicit in the
>> commit message.
>>
> 
> OK, will add explicit commit message, or, drop this patch if needed.

The patch is correct, so keep it please.  However, mention in the commit
message that the CPUID values were valid even before this patch.

Also, the QEMU side needs support for transferring the state in and out
of KVM (kvm_put_xsave, kvm_get_xsave).  On top of this you can add
migration support using a new subsection of vmstate_cpu.

Thanks!

Paolo

> Thanks,
> Jinsong
> 
>>
>>> Signed-off-by: Liu Jinsong <jinsong.liu@intel.com>
>>> ---
>>>  target-i386/cpu.c |    6 +++---
>>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
>>> index 864c80e..544b57f 100644
>>> --- a/target-i386/cpu.c
>>> +++ b/target-i386/cpu.c
>>> @@ -335,7 +335,7 @@ typedef struct ExtSaveArea {
>>>
>>>  static const ExtSaveArea ext_save_areas[] = {
>>>      [2] = { .feature = FEAT_1_ECX, .bits = CPUID_EXT_AVX,
>>> -            .offset = 0x100, .size = 0x240 },
>>> +            .offset = 0x240, .size = 0x100 },
>>>  };
>>>
>>>  const char *get_register_name_32(unsigned int reg)
>>> @@ -2225,8 +2225,8 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t
>>>              index, uint32_t count, const ExtSaveArea *esa =
>>>              &ext_save_areas[count]; if
>>>                  ((env->features[esa->feature] & esa->bits) ==
>>> esa->bits && (kvm_mask & (1 << count)) != 0) { 
>>> -                *eax = esa->offset;
>>> -                *ebx = esa->size;
>>> +                *eax = esa->size;
>>> +                *ebx = esa->offset;
>>>              }
>>>          }
>>>          break;
>>> --
>>> 1.7.1
> 

  reply	other threads:[~2013-11-29 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 13:15 [Qemu-devel] [PATCH 1/2] target-i386: fix cpuid leaf 0x0d Liu, Jinsong
2013-11-29 13:25 ` Paolo Bonzini
2013-11-29 14:46   ` Liu, Jinsong
2013-11-29 15:11     ` Paolo Bonzini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-02 16:41 Liu, Jinsong
2013-12-02 17:35 ` 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=5298AEAE.2070908@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@redhat.com \
    --cc=haoxudong.hao@gmail.com \
    --cc=jinsong.liu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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 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).