On 9/16/08, Anthony Liguori <[EMAIL PROTECTED]> wrote: > This patch refactors the AIO layer to allow multiple AIO implementations. > It's > only possible because of the recent signalfd() patch.
> +/* This is a simple lock used to protect the aio_handlers list. > Specifically, > + * it's used to ensure that no callbacks are removed while we're walking and > + * dispatching callbacks. > + */ > +static int walking_handlers; Shouldn't this be volatile and/or atomic_t? Just wondering, why don't you use real locking operations, for example those in qemu-lock.h? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
