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] the ptwr cmpxchg fix

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] the ptwr cmpxchg fix
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 19 Oct 2007 15:50:43 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 19 Oct 2007 15:51:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C33E1F20.F1A8%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <C33E1F20.F1A8%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.5 (X11/20070727)
Keir Fraser wrote:
> On 18/10/07 20:58, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:
>
>   
>>     * To quote Jan Beulich:
>>
>> Subject: [Xen-devel] c/s 15147 change to struct vcpu_register_vcpu_info
>>
>> 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.
>>
>> We don't use this on Solaris yet, however
>>     
>
> Since the old structure layout was never present in a stable release of Xen
> (that operation was not supported at all in 3.1.0) this one doesn't really
> belong on the incompatibility list.
>   

I think the structure was present, but there was no implementation to
back it up.  It's remotely possible someone decided to implement the
vcpu_info placement without ever testing it, but it seems unlikely.

    J

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

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