xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: freezing of kernel threads
Date: Tue, 27 Nov 2012 11:47:50 -0500	[thread overview]
Message-ID: <20121127164750.GA27586@phenom.dumpdata.com> (raw)
In-Reply-To: <50AE18CA02000078000AA90F@nat28.tlf.novell.com>

On Thu, Nov 22, 2012 at 11:21:30AM +0000, Jan Beulich wrote:
> Keir,
> 
> in linux-2.6.18-xen.hg c/s 74:cb50d25a9468 you made blktap
> match blkback in calling try_to_freeze() from the main thread loop.
> Threads in other drivers didn't get changed, though. Is there a
> particular reason why only block, and only backend, threads are in
> need of this (the only other one using it is xenfb_thread())?
> 
> Konrad, as of 2.6.23 kernel threads are non-freezable by default,
> i.e. xen-blkback calling try_to_freeze() is completely pointless
> without a prior call to set_freezable(). Also, in case the latter is to
> be added, switching to wait_event_freezable() instead of the
> direct use of try_to_freeze() might be the right way to go.

OK, any idea why the need to be come freezable was added in? Just
for power suspend/resume?

> 
> Jan
> 

  parent reply	other threads:[~2012-11-27 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 11:21 freezing of kernel threads Jan Beulich
2012-11-22 12:38 ` Keir Fraser
2012-11-27 16:47 ` Konrad Rzeszutek Wilk [this message]
2012-11-27 16:52   ` Jan Beulich

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=20121127164750.GA27586@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).