From: Borislav Petkov <borislav.petkov@amd.com>
To: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
<mingo@redhat.com>, <hpa@zytor.com>,
<linux-kernel@vger.kernel.org>, <sp@numascale.com>,
<bp@amd64.org>, <tglx@linutronix.de>, <daniel@numascale-asia.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: [PATCH resend] x86/platform: Remove incorrect error message in x86_default_fixup_cpu_id()
Date: Mon, 16 Apr 2012 19:31:46 +0200 [thread overview]
Message-ID: <20120416173146.GA4838@aftab> (raw)
In-Reply-To: <20120404123809.GB5193@x1.osrc.amd.com>
On Wed, Apr 04, 2012 at 02:38:09PM +0200, Borislav Petkov wrote:
> On Mon, Apr 02, 2012 at 06:06:48PM +0200, Andreas Herrmann wrote:
> >
> > It's only called from amd.c:srat_detect_node(). The introduced
> > condition for calling the fixup code is true for all AMD multi-node
> > processors, e.g. Magny-Cours and Interlagos. There we have 2 NUMA
> > nodes on one socket. Thus there are cores having different
> > numa-node-id but with equal phys_proc_id.
> >
> > There is no point to print error messages in such a situation.
> >
> > The confusing/misleading error message was introduced with commit
> > 64be4c1c2428e148de6081af235e2418e6a66dda (x86: Add x86_init platform
> > override to fix up NUMA core numbering).
> >
> > Remove the default fixup function (especially the error message) and
> > replace it by a NULL pointer check, move the Numascale-specific
> > condition for calling the fixup into the fixup-function itself and
> > slightly adapt the comment.
> >
> > Cc: <stable@kernel.org>
> > Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
> > ---
> > arch/x86/include/asm/x86_init.h | 1 -
> > arch/x86/kernel/apic/apic_numachip.c | 7 +++++--
> > arch/x86/kernel/cpu/amd.c | 7 ++++---
> > arch/x86/kernel/cpu/common.c | 9 ---------
> > arch/x86/kernel/x86_init.c | 1 -
> > 5 files changed, 9 insertions(+), 16 deletions(-)
> >
> > This patch didn't make it into v3.3.
> > But the misleading error message introduced with numachip support was
> > merged.
>
> Yes, please apply this one, I still get the following on my box with
> 3.4-rc1+:
>
> [ 0.382396] Booting Node 0, Processors #1 #2 #3 #4 #5 Ok.
> [ 0.454471] Booting Node 1, Processors #6
> [ 0.469600] NUMA core number 1 differs from configured core number 0
> [ 0.478361] #7
> [ 0.490949] NUMA core number 1 differs from configured core number 0
> [ 0.499695] #8
> [ 0.512577] NUMA core number 1 differs from configured core number 0
> [ 0.521331] #9
> [ 0.533921] NUMA core number 1 differs from configured core number 0
> [ 0.542679] #10
> [ 0.555340] NUMA core number 1 differs from configured core number 0
> [ 0.564088] #11
> [ 0.576730] NUMA core number 1 differs from configured core number 0
Still happens on -rc3. Ingo, can we please merge the above fix before 3.4
is out?
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-04-16 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 17:17 [PATCH] x86: Remove wrong error message in x86_default_fixup_cpu_id Andreas Herrmann
2012-02-21 10:27 ` Borislav Petkov
2012-02-21 11:05 ` Daniel J Blueman
2012-02-21 11:20 ` Borislav Petkov
2012-02-21 12:56 ` Daniel J Blueman
2012-02-22 13:47 ` Andreas Herrmann
2012-02-23 10:23 ` Daniel J Blueman
2012-02-24 15:31 ` [PATCH resend] " Andreas Herrmann
2012-02-27 12:07 ` [tip:x86/platform] x86/platform: Remove incorrect error message in x86_default_fixup_cpu_id() tip-bot for Andreas Herrmann
2012-02-28 15:27 ` Borislav Petkov
2012-02-28 16:42 ` [tip:x86/urgent] " tip-bot for Andreas Herrmann
2012-03-02 11:04 ` Ingo Molnar
2012-03-02 11:51 ` Andreas Herrmann
2012-04-02 16:06 ` [PATCH resend] " Andreas Herrmann
2012-04-04 12:38 ` Borislav Petkov
2012-04-16 17:31 ` Borislav Petkov [this message]
2012-04-16 18:53 ` [tip:x86/urgent] " tip-bot for Andreas Herrmann
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=20120416173146.GA4838@aftab \
--to=borislav.petkov@amd.com \
--cc=andreas.herrmann3@amd.com \
--cc=bp@alien8.de \
--cc=bp@amd64.org \
--cc=daniel@numascale-asia.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sp@numascale.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).