From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Paul Jackson <pj@sgi.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
gregkh@suse.de, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [git pull for -mm] CPU isolation extensions (updated2)
Date: Tue, 12 Feb 2008 17:41:21 +1100 [thread overview]
Message-ID: <200802121741.22201.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <47B11C45.6060408@qualcomm.com>
On Tuesday 12 February 2008 15:10, Max Krasnyansky wrote:
> Rusty - Stop machine.
> After doing a bunch of testing last three days I actually downgraded
> stop machine changes from [highly experimental] to simply [experimental].
> Pleas see this thread for more info:
> http://marc.info/?l=linux-kernel&m=120243837206248&w=2 Short story is that
> I ran several insmod/rmmod workloads on live multi-core boxes with stop
> machine _completely_ disabled and did no see any issues. Rusty did not get
> a chance to reply yet, I hopping that we'll be able to make "stop machine"
> completely optional for some configurations.
stop machine is used for more than just module loading and unloading.
I don't think you can just disable it.
next prev parent reply other threads:[~2008-02-12 6:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 4:10 Max Krasnyansky
2008-02-12 6:41 ` Nick Piggin [this message]
2008-02-12 6:44 ` David Miller
2008-02-13 3:32 ` Max Krasnyansky
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=200802121741.22201.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®