Re: [Xen-devel] unregister_xenbus_watch() handling of xenwatch_mutex

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

That's a question for Jeremy. I think the 2.6.18 version is equally correct
and only needs one if statement. Maybe hoisting the lock acquisition gave
Jeremy a warmer fuzzy feeling? :-)

 -- Keir

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

> 2.6.23 acquires the mutex before canceling pending events, whereas
> linux-2.6.18-xen acquires and releases the mutex back-to-back after
> doing the cancellation. It would seem to me that the former method is
> more robust, but otoh I'm wondering why this change then wasn't also
> made in the 2.6.18 tree.
> 
> Thanks, 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