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

[Xen-devel] [PATCH v2 0/3] Introduce a fpu_initilised filed to HVM CPU context

To: <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Roger Pau Monne <roger.pau@xxxxxxxxxx>
Date: Tue, 17 Nov 2015 18:44:36 +0000
Delivery-date: Tue, 17 Nov 2015 18:45: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.

Roger.

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

Follow-Ups:
- [Xen-devel] [PATCH v2 3/3] Revert "libxc: create an initial FPU state for HVM guests"
  - From: Roger Pau Monne
- [Xen-devel] [PATCH v2 2/3] xen/hvm: introduce a fpu_uninitialised field to the CPU save record
  - From: Roger Pau Monne
- [Xen-devel] [PATCH v2 1/3] xen/save: pass a size paramter to the HVM compat functions
  - From: Roger Pau Monne

Prev by Date: [Xen-devel] [PATCH v2 1/3] xen/save: pass a size paramter to the HVM compat functions
Next by Date: [Xen-devel] [PATCH v2 2/3] xen/hvm: introduce a fpu_uninitialised field to the CPU save record
Previous by thread: [Xen-devel] Fwd: Question regarding the behavior of guest_physmap_remove_page on x86
Next by thread: [Xen-devel] [PATCH v2 1/3] xen/save: pass a size paramter to the HVM compat functions
Index(es):
- Date
- Thread

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