On 04/06/12 03:57, Rusty Russell wrote: > Unfortunately, this conflicts with Asias He's deadlock fix, which has > us just using the block-layer-supplied spinlock. > > If we drop the lock around the kick as you suggest, we're playing with > fire. All the virtio backends have an atomic notify, so they're OK, > and the block layer *looks* safe at a glance, but there's no assurances. Well, the kick itself returns early, but in the host every other action is already asynchronously running - not caring about the guest locks at all. So if removing the lock around the kick causes a problem, then the problem is already present, no? Christian _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
