Re: [Xen-devel] c/s 20384

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

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...

    J

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