[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200802121741.22201.nickpiggin@yahoo.com.au>
Date: Tue, 12 Feb 2008 17:41:21 +1100
From: Nick Piggin <nickpiggin@...oo.com.au>
To: Max Krasnyansky <maxk@...lcomm.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>, Paul Jackson <pj@....com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, gregkh@...e.de,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [git pull for -mm] CPU isolation extensions (updated2)
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists