From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: freezing of kernel threads
Date: Thu, 22 Nov 2012 12:38:22 +0000 [thread overview]
Message-ID: <CCD3CD3E.452D4%keir.xen@gmail.com> (raw)
In-Reply-To: <50AE18CA02000078000AA90F@nat28.tlf.novell.com>
On 22/11/2012 11:21, "Jan Beulich" <JBeulich@suse.com> 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())?
I don't really recall. I expect someone pointed out the difference between
the two drivers and so I added the call to blktap. Back then I don't know
that any of our other drivers had kthreads?
-- Keir
> 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.
>
> Jan
>
next prev parent reply other threads:[~2012-11-22 12:38 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 [this message]
2012-11-27 16:47 ` Konrad Rzeszutek Wilk
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=CCD3CD3E.452D4%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--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 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.