From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: [patch 0/2] stop_machine: create kstop threads only when needed
Date: Mon, 22 Dec 2008 12:36:29 +0100 [thread overview]
Message-ID: <20081222113629.080104676@de.ibm.com> (raw)
Introduce stop_machine_create/destroy. With this interface subsystems
that need a non-failing stop_machine environment can create the
stop_machine threads before actually calling stop_machine.
When the threads aren't needed anymore they can be killed with
stop_machine_destroy again.
When stop_machine gets called and the threads aren't present they
will be created and destroyed automatically.
This restores the old behaviour of stop_machine from 2.6.27 and thus
we get rid of the normally not needed kstop threads.
The second patch converts the module loader/unloder code to the new
interface, since it needs a non-failing stop_machine infrastructure.
Looks like there are more users that need a non-failing version.
I'll take care of them when I'm back from vacation.
next reply other threads:[~2008-12-22 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 11:36 Heiko Carstens [this message]
2008-12-22 11:36 ` [patch 1/2] stop_machine: introduce stop_machine_create/destroy Heiko Carstens
2009-01-27 8:04 ` [Bug 12492] " Andrew Morton
2009-01-27 9:52 ` Andrew Morton
2009-01-27 10:09 ` Heiko Carstens
2008-12-22 11:36 ` [patch 2/2] module: convert to stop_machine_create/destroy Heiko Carstens
2008-12-25 13:07 ` [patch 0/2] stop_machine: create kstop threads only when needed Rusty Russell
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=20081222113629.080104676@de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.