WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info

To: Jan Beulich <jbeulich@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 18 Oct 2007 14:19:50 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 18 Oct 2007 06:21:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4717756D.76E4.0078.0@xxxxxxxxxx>
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
Thread-index: AcgRiY/AzpdabH18Edyp5QAX8io7RQ==
Thread-topic: [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info
User-agent: Microsoft-Entourage/11.3.6.070618
Xen 3.1.0 does not support that vcpu operation. 3.1.1 is the first stable
Xen release to support it. The old definition in 2.6.23 is a bug, and I
believe Jeremy already has a fix for 2.6.24.

The structure re-definition was to allow extensibility and to avoid having
to implement 32-on-64 shim code.

 -- Keir

On 18/10/07 14:02, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> 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



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

<Prev in Thread] Current Thread [Next in Thread>