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

[Xen-devel] [PATCH v3 0/4] Introduce a fpu_initilised field to HVM CPU context

To: <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Roger Pau Monne <roger.pau@xxxxxxxxxx>
Date: Wed, 18 Nov 2015 16:37:07 +0000
Delivery-date: Wed, 18 Nov 2015 16:41:15 +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 v3 2/4] xen/save: allow the usage of zeroextend and a fixup function
  - From: Roger Pau Monne
- [Xen-devel] [PATCH v3 1/4] xen/save: pass a size parameter to the HVM compat functions
  - From: Roger Pau Monne
- [Xen-devel] [PATCH v3 3/4] xen/hvm: introduce a fpu_uninitialised field to the CPU save record
  - From: Roger Pau Monne
- [Xen-devel] [PATCH v3 4/4] Revert "libxc: create an initial FPU state for HVM guests"
  - From: Roger Pau Monne

Prev by Date: [Xen-devel] [PATCH v3 3/4] xen/hvm: introduce a fpu_uninitialised field to the CPU save record
Next by Date: [Xen-devel] [PATCH v3 1/4] xen/save: pass a size parameter to the HVM compat functions
Previous by thread: [Xen-devel] [PATCH 4.6] Config: Switch to unified qemu trees.
Next by thread: [Xen-devel] [PATCH v3 4/4] 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®.