[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v5 2/3] xen/hvm: introduce a flags field in the CPU save record

To: Roger Pau Monne <roger.pau@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Tue, 1 Dec 2015 13:43:16 +0000
Cc: Jan Beulich <jbeulich@xxxxxxxx>
Delivery-date: Tue, 01 Dec 2015 13:43:25 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 01/12/15 12:47, Roger Pau Monne wrote:
> Introduce a new flags field and use bit 0 to signal if the FPU has been
> initialised or not. Previously Xen always wrongly assumed the FPU was
> initialised on restore.
>
> Signed-off-by: Roger Pau MonnÃ <roger.pau@xxxxxxxxxx>

Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH v5 0/3] Introduce a flags field to HVM CPU context
  - From: Roger Pau Monne
- [Xen-devel] [PATCH v5 2/3] xen/hvm: introduce a flags field in the CPU save record
  - From: Roger Pau Monne

Prev by Date: Re: [Xen-devel] [PATCH v5 1/3] xsave: fix initialization of FPU memory area
Next by Date: Re: [Xen-devel] [PATCH 1/2] xen: wrap xenbus on xenfs with COMPAT option
Previous by thread: [Xen-devel] [PATCH v5 2/3] xen/hvm: introduce a flags field in the CPU save record
Next by thread: [Xen-devel] [PATCH v5 3/3] Revert "libxc: create an initial FPU state for HVM guests"
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.