All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: XSAVE/XRSTOR live migration support
Date: Mon, 31 May 2010 14:26:01 +0300	[thread overview]
Message-ID: <4C039CC9.20103@redhat.com> (raw)
In-Reply-To: <201005311921.10566.sheng@linux.intel.com>

On 05/31/2010 02:21 PM, Sheng Yang wrote:
>
>> Need to reserve way more space here for future xsave growth.  I think at
>> least 4K.  LRB wa 32x512bit = 1K (though it probably isn't a candidate
>> for vmx).  Would be good to get an opinion from your processor architects.
>>
>> I don't think we need to detail the contents of the structures since
>> they're described by the SDM; so we can have just a large array that is
>> 1:1 with the xsave as saved by the fpu.
>>      
> I think we can reserve one page here. But one big array make it harder to work
> with QEmu CPUState. Do we need lots of marcos in QEmu to parse the array? Also
> it's easier to transfer get/set_fpu to get/set_xsave interface using current
> structure I think.
>    

We'll need that code somewhere, so we aren't losing anything by putting 
it in userspace (in fact, qemu already has to have most of this code 
since it supports fxsave/fxrstor emulation).

What we gain is that if we make a bug, it is easier to fix it in 
userspace than in the kernel.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


      reply	other threads:[~2010-05-31 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  9:48 [PATCH] KVM: x86: XSAVE/XRSTOR live migration support Sheng Yang
2010-05-27 10:02 ` Avi Kivity
2010-05-27 10:33   ` Sheng Yang
2010-05-27 11:34     ` Avi Kivity
2010-05-31 11:21   ` Sheng Yang
2010-05-31 11:26     ` Avi Kivity [this message]

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=4C039CC9.20103@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.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.