From: Max Krasnyansky <maxk@qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: nickpiggin@yahoo.com.au, akpm@linux-foundation.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, pj@sgi.com, a.p.zijlstra@chello.nl,
gregkh@suse.de, rusty@rustcorp.com.au
Subject: Re: [git pull for -mm] CPU isolation extensions (updated2)
Date: Tue, 12 Feb 2008 19:32:51 -0800 [thread overview]
Message-ID: <47B264E3.4090605@qualcomm.com> (raw)
In-Reply-To: <20080211.224436.174153780.davem@davemloft.net>
David Miller wrote:
> From: Nick Piggin <nickpiggin@yahoo.com.au>
> Date: Tue, 12 Feb 2008 17:41:21 +1100
>
>> stop machine is used for more than just module loading and unloading.
>> I don't think you can just disable it.
>
> Right, in particular it is used for CPU hotplug.
Ooops. Totally missed that. And a bunch of other places.
[maxk@duo2 cpuisol-2.6.git]$ git grep -l stop_machine_run
Documentation/cpu-hotplug.txt
arch/s390/kernel/kprobes.c
drivers/char/hw_random/intel-rng.c
include/linux/stop_machine.h
kernel/cpu.c
kernel/module.c
kernel/stop_machine.c
mm/page_alloc.c
I wonder why I did not see any issues when I disabled stop machine completely.
I mentioned in the other thread that I commented out the part that actually halts
the machine and ran it for several hours on my dual core laptop and on the quad
core server. Tried all kinds of workloads, which include constant module removal
and insertion, and cpu hotplug as well. It cannot be just luck :).
Clearly though, you guys are right. It cannot be simply disabled. Based on the
above grep it's needed for CPU hotplug, mem hotplug, kprobes on s390 and intel
rng driver. Hopefully we can avoid it at least in module insertion/removal.
Max
next prev parent reply other threads:[~2008-02-13 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 4:10 [git pull for -mm] CPU isolation extensions (updated2) Max Krasnyansky
2008-02-12 6:41 ` Nick Piggin
2008-02-12 6:44 ` David Miller
2008-02-13 3:32 ` Max Krasnyansky [this message]
2008-02-13 4:11 ` Nick Piggin
2008-02-13 6:06 ` Max Krasnyansky
2008-02-13 6:22 ` Nick Piggin
2008-02-13 17:11 ` Max Krasnyansky
2008-02-12 18:59 ` Peter Zijlstra
2008-02-13 3:59 ` Max Krasnyansky
2008-02-13 5:19 ` Steven Rostedt
2008-02-13 5:47 ` Max Krasnyansky
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=47B264E3.4090605@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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).