[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 08/19] libxc: suspend: Fix suspend event channel locking
Shriram Rajagopalan writes ("Re: [PATCH 08/19] libxc: suspend: Fix suspend event channel locking"): > On Tue, Mar 4, 2014 at 6:56 AM, Ian Jackson <ian.jackson@xxxxxxxxxxxxx> wrote: > > Use fcntl F_SETLK, rather than writing our pid into a "lock" file. > That way if we crash we don't leave the lockfile lying about. Callers > now need to keep the fd for our lockfile. (We don't use flock because > we don't want anyone who inherits this fd across fork to end up with a > handle onto the lock.) ... > Acked-by: Shriram Rajagopalan <rshriram@xxxxxxxxx> Thanks. > Slightly off-track: > If you got a chance to test this patch, were you able to live migrate more > than one > domain simultaneously? I don't see any reason why it shouldn't be possible > but I sort of vaguely remember some bug fix in the past, where we couldn't > start more than one live migration at the same time I will test that. Thanks, Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |