linux-kernel - Re: [patch 1/2] add ALL_CPUS option to stop_machine

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47CCCBDE.6040609@qualcomm.com>
Date:	Mon, 03 Mar 2008 20:11:10 -0800
From:	Max Krasnyansky <maxk@...lcomm.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Ingo Molnar <mingo@...e.hu>, Jason Baron <jbaron@...hat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch 1/2] add ALL_CPUS option to stop_machine_run()



Rusty Russell wrote:
> On Tuesday 04 March 2008 11:30:52 Max Krasnyanskiy wrote:
>> Great. I might get some time later this week to think about this some more
>> and try things out. So if you have ideas/suggestions let me know.
> 
> Hmm, might be worth making stop_machine_run take a cpumask: I balked at it 
> originally, but introducing a section special case crosses the line I think.

Are you talking about a mask of which CPUs to stop  ?
That's essentially what I did with the cpu_isolated_map. But as Ingo and
others pointed out it's the wrong thing to do.
Or did you mean something else ?

Max
--
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/