Re: [PATCH 14/14] Don't mark suspend as active until we know it is running

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/29/2011 08:44 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
> 
> If suspend failed for some reason (eg too short duration) then

s/eg/e.g./

> susquent attempts to trigger suspend were rejected because we

s/susquent/subsequent/

> had already marked a suspend as being in progress
> 
> * src/util/virnodesuspend.c: Don't mark suspend as active
>   until we've successfully triggered it
> ---
>  src/util/virnodesuspend.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

ACK.  As long as we only mark aboutToSuspend while holding the lock, and
only ever probe it while also holding the lock, then we're safe.

-- 
Eric Blake   eblake@xxxxxxxxxx    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]