From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, hpa@zytor.com, x86@kernel.org,
eric.dumazet@gmail.com, yinghai@kernel.org, brgerst@gmail.com,
gorcunov@gmail.com, penberg@kernel.org, shaohui.zheng@intel.com
Subject: Re: [PATCHSET] x86: unify x86_32 and 64 NUMA init paths, take#3
Date: Thu, 16 Dec 2010 17:30:41 +0100 [thread overview]
Message-ID: <4D0A3EB1.7060207@kernel.org> (raw)
In-Reply-To: <1292074247-20891-1-git-send-email-tj@kernel.org>
(cc'ing Shaohui)
Hello, Thoams.
On 12/11/2010 02:30 PM, Tejun Heo wrote:
> This is the third take of unify-x86_32-and-64-NUMA-init-paths
> patchset. Most changes from the last take[L] are to reflect comments
> from tglx.
>
> * Rebased on top of tip/x86/apic-cleanup.
>
> * "x86: apic: Cleanup and simplify setup_local_APIC()" is already
> merged into x86/apic-cleanup and dropped from this series.
>
> * Instead of repurposing apic->cpu_to_logical_apicid(), replace it
> with a new 32bit specific callback
> apic->x86_32_early_logical_apicid().
>
> * For consistency, in 0012, apic->apicid_to_node() is renamed to
> x86_32_numa_cpu_node() and put inside CONFIG_X86_32.
>
> * NULL assignments for unimplemented apic ops dropped.
>
> * 0013 now explicitly describes why amd srat_detect_node() accesses
> __apicid_to_node[] directly. Also, add a comment in the function
> noting the ugliness.
>
> * Patch description updated in 0014.
>
> * Other misc updates.
Do the above changes agreeable to you? Shaohui is wondering what to
do with the conflicts between the NUMA hotplug simulator and this
series, so...
Thank you.
--
tejun
next parent reply other threads:[~2010-12-16 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1292074247-20891-1-git-send-email-tj@kernel.org>
2010-12-16 16:30 ` Tejun Heo [this message]
2010-12-16 16:56 ` Thomas Gleixner
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=4D0A3EB1.7060207@kernel.org \
--to=tj@kernel.org \
--cc=brgerst@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=shaohui.zheng@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®