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

RE: [Xen-devel] RE: [Xen-changelog] [xen-unstable] Initial support for HVM compat guests


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Mon, 15 Jan 2007 16:57:54 +0800
  • Delivery-date: Mon, 15 Jan 2007 00:57:39 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccxDEI/xnx7jpkDRTyKsEVGkKWVRwHYc7AQAAKt9UUAAFJcwAAA2gytAAAgxHAAAKYEUwAApo0Q
  • Thread-topic: [Xen-devel] RE: [Xen-changelog] [xen-unstable] Initial support for HVM compat guests

>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年1月15日 16:39
>
>Hmmm there is underlying code shared by both compat and native
>hypercall
>layer that will check IS_COMPAT. So jumping at the compat layer is
>insufficient (even though that is precisely what the hvm hypercall
>wrapper
>does).
>
>Basically this work isn't complete yet. Probably what will happen is that
>the IS_COMPAT() test will be made per-vcpu rather than per-domain and
>we
>will set the per-vcpu flag correctly for an hvm guest at least whenever it
>vmexits for a hypercall. Or we will make IS_COMPAT() look at
>shadow-mode
>guest_levels if it is invoked on an HVM vcpu.
>
> -- Keir

OK, the status is clearer to me now. Thanks a lot,
- Kevin

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


 


Rackspace

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