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

[Xen-devel] Backporting cpuid faulting to Xen-4.1.0

To: Keir Fraser <keir.xen@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
Date: Fri, 16 Sep 2011 18:19:33 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "Shan, Haitao" <haitao.shan@xxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>
Delivery-date: Fri, 16 Sep 2011 03:21:11 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: Acx0WiEbENBnkoS7T5OXYJSbSkwJNQ==
Thread-topic: Backporting cpuid faulting to Xen-4.1.0

Keir,

In July we implemented cpuid faulting feature, and checked in xen-unstable tree 
as c/s 23653/23654/23655.

Today we patched them to xen-4.1.0, test result shows it's OK to work with 
xen-4.1.0.
So how about backporting this feature to xen-4.1.0?

Thanks,
Jinsong
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- [Xen-devel] Re: Backporting cpuid faulting to Xen-4.1.0
  - From: Keir Fraser

Prev by Date: [Xen-devel] [PATCH] x86/tboot: make resume error messages visible
Next by Date: [Xen-devel] [PATCH] x86/vmx: don't call __vmxoff() blindly
Previous by thread: [Xen-devel] [PATCH] x86/tboot: make resume error messages visible
Next by thread: [Xen-devel] Re: Backporting cpuid faulting to Xen-4.1.0
Index(es):
- Date
- Thread

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