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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 20 Nov 2008 09:20:13 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-kernel@...r.kernel.org, Mike Travis <travis@....com>,
	ink@...assic.park.msu.ru, rmk@....linux.org.uk, starvik@...s.com,
	tony.luck@...el.com, takata@...ux-m32r.org, ralf@...ux-mips.org,
	grundler@...isc-linux.org, paulus@...ba.org,
	schwidefsky@...ibm.com, lethal@...ux-sh.org, wli@...omorphy.com,
	davem@...emloft.net, jdike@...toit.com, mingo@...hat.com
Subject: Re: [PATCH 1/2] cpumask: centralize cpu_online_map and
	cpu_possible_map


* Rusty Russell <rusty@...tcorp.com.au> wrote:

> (I'll be rinsing this through linux-next; testing feedback and even 
> Acked-by's appreciated).
> 
> Each SMP arch defines these themselves.  Move them to a central 
> location.
> 
> Twists:
> 1) Some archs (m32, parisc, s390) set possible_map to all 1, so we add a
>    CONFIG_INIT_ALL_POSSIBLE for this rather than break them.
> 
> 2) mips and sparc32 '#define cpu_possible_map phys_cpu_present_map'.
>    Those archs simply have phys_cpu_present_map replaced everywhere.
> 
> 3) Alpha defined cpu_possible_map to cpu_present_map; this is tricky
>    so I just manipulate them both in sync.
> 
> 4) IA64, cris and m32r have gratuitous 'extern cpumask_t cpu_possible_map'
>    declarations.
> 
> Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>

Nice cleanup - my earlier acked-by for this concept still stands:

  Acked-by: Ingo Molnar <mingo@...e.hu>

	Ingo
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ