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

[Xen-devel] [PATCH v5 0/3] Introduce a flags field to HVM CPU context

To: <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Roger Pau Monne <roger.pau@xxxxxxxxxx>
Date: Tue, 1 Dec 2015 13:47:02 +0100
Delivery-date: Tue, 01 Dec 2015 12:47:14 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

Hello,

This patch series tries to properly solve the problem seen with the HVMlite 
series, that Xen always assumes the FPU is initialised on CPU context 
restore.

Patch 1/3 is new in this iteration of the series, and aims to unify the way 
FPU area memory is initialised on xsave capable hosts vs non-xsave capable 
ones.

Roger.

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

Follow-Ups:
- [Xen-devel] [PATCH v5 3/3] Revert "libxc: create an initial FPU state for HVM guests"
  - 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
- [Xen-devel] [PATCH v5 1/3] xsave: fix initialization of FPU memory area
  - From: Roger Pau Monne

Prev by Date: Re: [Xen-devel] Xen 4.7 Development Update
Next by Date: [Xen-devel] [PATCH v5 1/3] xsave: fix initialization of FPU memory area
Previous by thread: Re: [Xen-devel] [PATCH] build: fix clean rule to cover objects in unvisited subdirs
Next by thread: [Xen-devel] [PATCH v5 1/3] xsave: fix initialization of FPU memory area
Index(es):
- Date
- Thread

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