From: David Vrabel <david.vrabel@citrix.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>,
<xen-devel@lists.xenproject.org>
Cc: <linux-kernel@vger.kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [Xen-devel] [PATCH] xen/manage: Fix USB interaction issues when resuming
Date: Mon, 19 Jan 2015 17:11:36 +0000 [thread overview]
Message-ID: <54BD3AC8.1040808@citrix.com> (raw)
In-Reply-To: <1421673578-12127-1-git-send-email-ross.lagerwall@citrix.com>
On 19/01/15 13:19, Ross Lagerwall wrote:
> Commit 61a734d305e1 ("xen/manage: Always freeze/thaw processes when
> suspend/resuming") ensured that userspace processes were always frozen
> before suspending to reduce interaction issues when resuming devices.
> However, freeze_processes() does not freeze kernel threads. Freeze
> kernel threads as well to prevent deadlocks with the khubd thread when
> resuming devices.
>
> This is what native suspend and resume does.
Applied to stable/for-linus-3.19, thanks.
David
prev parent reply other threads:[~2015-01-19 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 13:19 Ross Lagerwall
2015-01-19 17:11 ` David Vrabel [this message]
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=54BD3AC8.1040808@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome