[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1308901534.27849.10.camel@twins>
Date: Fri, 24 Jun 2011 09:45:34 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: "mingo@...e.hu" <mingo@...e.hu>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>,
"trenn@...ell.com" <trenn@...ell.com>,
"prarit@...hat.com" <prarit@...hat.com>,
"tj@...nel.org" <tj@...nel.org>,
"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Song, Youquan" <youquan.song@...el.com>
Subject: Re: [patch 3/4] stop_machine: implement
stop_machine_from_offline_cpu()
On Thu, 2011-06-23 at 11:19 -0700, Suresh Siddha wrote:
> > In commit d0af9eed5aa91b6b7b5049cae69e5ea956fd85c3 you mention that its
> > specific to HT, wouldn't it make sense to limit the stop-machine use in
> > the next patch to the sibling mask instead of the whole machine?
>
> That specific issue was seen in the context of HT. But the SDM
> guidelines (pre date HT and) are applicable for SMP too.
Sure, but we managed to ignore those long enough, could we not continue
to violate them and keep to the minimum that is working in practice?
>From what I understand the explosion is WSM+/VMX on HT only because the
siblings share state, or do we have proof that it yields problems
between cores as well?
--
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