From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
ink@jurassic.park.msu.ru, rmk@arm.linux.org.uk, starvik@axis.com,
tony.luck@intel.com, takata@linux-m32r.org, ralf@linux-mips.org,
grundler@parisc-linux.org, paulus@samba.org,
schwidefsky@de.ibm.com, lethal@linux-sh.org, wli@holomorphy.com,
davem@davemloft.net, jdike@addtoit.com, mingo@redhat.com
Subject: Re: [PATCH 1/2] cpumask: centralize cpu_online_map and cpu_possible_map
Date: Thu, 20 Nov 2008 09:20:13 +0100 [thread overview]
Message-ID: <20081120082013.GF21785@elte.hu> (raw)
In-Reply-To: <200811200107.18162.rusty@rustcorp.com.au>
* Rusty Russell <rusty@rustcorp.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@rustcorp.com.au>
Nice cleanup - my earlier acked-by for this concept still stands:
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
prev parent reply other threads:[~2008-11-20 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 14:37 [PATCH 1/2] cpumask: centralize cpu_online_map and cpu_possible_map Rusty Russell
2008-11-19 18:17 ` Russell King
2008-11-19 23:30 ` Rusty Russell
2008-11-20 5:10 ` Grant Grundler
2008-11-20 8:20 ` Ingo Molnar [this message]
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=20081120082013.GF21785@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=grundler@parisc-linux.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jdike@addtoit.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=tony.luck@intel.com \
--cc=travis@sgi.com \
--cc=wli@holomorphy.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.