All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>,
	xen-devel@lists.xenproject.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH] xen/manage: Always freeze/thaw processes when suspend/resuming
Date: Fri, 22 Aug 2014 12:00:57 +0100	[thread overview]
Message-ID: <53F722E9.4060505@citrix.com> (raw)
In-Reply-To: <1408354896-30770-1-git-send-email-ross.lagerwall@citrix.com>

On 18/08/14 10:41, Ross Lagerwall wrote:
> Always freeze processes when suspending and thaw processes when resuming
> to prevent a race noticeable with HVM guests.
> 
> This prevents a deadlock where the khubd kthread (which is designed to
> be freezable) acquires a usb device lock and then tries to allocate
> memory which requires the disk which hasn't been resumed yet.
> Meanwhile, the xenwatch thread deadlocks waiting for the usb device
> lock.
> 
> Freezing processes fixes this because the khubd thread is only thawed
> after the xenwatch thread finishes resuming all the devices.

I think this is the safest fix for this issue but I'm a bit concerned
about how much extra time the freeze_processes() call will add to the
suspend.

Can you measure how long it takes for a typical VM?

David

  reply	other threads:[~2014-08-22 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18  9:41 [PATCH] xen/manage: Always freeze/thaw processes when suspend/resuming Ross Lagerwall
2014-08-22 11:00 ` David Vrabel [this message]
2014-08-22 14:39   ` Ross Lagerwall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53F722E9.4060505@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.