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/
Home Products Support Community News


Re: [Xen-devel] c/s 20384

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] c/s 20384
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 02 Nov 2009 13:08:36 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 02 Nov 2009 13:09:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AEEA3BB020000780001D146@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4AEEA3BB020000780001D146@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4
On 11/02/09 00:17, Jan Beulich wrote:
> Keir,
> I'm having the impression that this c/s unintentionally modifies behavior in
> certain ways:
> - map_vcpu_info() no longer sets evtchn_upcall_mask for a newly mapped
> info struct
> - VCPUOP_initialise no longer fails when a vCPU didn't have a proper info
> struct installed
> - the changes to xen/common/event_channel.c make it so that
> dummy_vcpu_info can be written to, and hence subsequently initialized
> vcpu_info structs would have unpredictable initial state

What's the real changeset id you're referring to?  The small-integer
numbers are only locally valid (and globally by coincidence), and 20384
here doesn't seem at all relevant to your points.

I you're referring to f74f0c1ae8ab, which is  21773 in my tree...


Xen-devel mailing list

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