All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weidong Han <weidong.han@intel.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH 2/4] XSAVE/XRSTOR: enable guest  save/restore
Date: Tue, 31 Aug 2010 20:28:09 +0800	[thread overview]
Message-ID: <4C7CF559.5010805@intel.com> (raw)
In-Reply-To: <C8A26E3B.21622%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> On 31/08/2010 08:08, "Jan Beulich" <JBeulich@novell.com> wrote:
>
>   
>>> #define VGCF_I387_VALID                (1<<0)
>>> #define VGCF_IN_KERNEL                 (1<<2)
>>> #define _VGCF_i387_valid               0
>>>       
>> As Keir already indicated, you can't change the size of this structure.
>> I'd say that it was a mistake to include the FPU state directly here in
>> the first place - you'll have to invent a mechanism to (compatibly)
>> not make this a requirement anymore. E.g. use the reserved part of
>> fpu_ctxt to store a guest handle referring to the actual area: This
>> ought to work as (iirc) the structure is used as input only
>> (VCPUOP_initialize) outside of the tools, and the domctl interface is
>> allowed to change as long as you don't break compatibility with
>> stored data (saved guest images).
>>     
>
> I would agree but for the fact that it appears that XSAVE is only supported
> for HVM guests right now. Hence this whole rigmarole is actually currently
> pointless, since HVM guests do not initialise/save/restore the
> vcpu_guest_context structure. I think probably this bit of the patch could
> simply be dropped until PV support is added.
>
>  -- Keir
>
> I will send out other patches soon, and revise this patch later.
Regards,
Weidong
>  
>   

      reply	other threads:[~2010-08-31 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31  2:59 [PATCH 2/4] XSAVE/XRSTOR: enable guest save/restore Han, Weidong
2010-08-31  7:08 ` Jan Beulich
2010-08-31  7:30   ` Keir Fraser
2010-08-31 12:28     ` Weidong Han [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=4C7CF559.5010805@intel.com \
    --to=weidong.han@intel.com \
    --cc=JBeulich@novell.com \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.