 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info
| To: | "Jeremy Fitzhardinge" <jeremy@xxxxxxxxxxxxx>, "Keir Fraser" <keir@xxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Thu, 18 Oct 2007 14:02:05 +0100 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Thu, 18 Oct 2007 06:01:22 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
This changeset changed the layout of the structure, and 3.1 as well as 2.6.23 use the old layout, while 3.1.1 uses to new one. I'm also puzzled about the need for an MFN to be uint64_t rather than xen_pfn_t. Thanks for clarification, Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] unregister_xenbus_watch() handling of xenwatch_mutex, Keir Fraser |
|---|---|
| Next by Date: | Re: [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info, Keir Fraser |
| Previous by Thread: | [Xen-devel] unregister_xenbus_watch() handling of xenwatch_mutex, Jan Beulich |
| Next by Thread: | Re: [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
