All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	sp@numascale.com, bp@amd64.org, tglx@linutronix.de,
	borislav.petkov@amd.com, 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: Wed, 4 Apr 2012 14:38:09 +0200	[thread overview]
Message-ID: <20120404123809.GB5193@x1.osrc.amd.com> (raw)
In-Reply-To: <20120402160648.GR27684@alberich.amd.com>

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
[    0.585497]  Ok.
[    0.587698] Booting Node   3, Processors  #12
[    0.602916] NUMA core number 3 differs from configured core number 1
[    0.709432]  #13
[    0.722106] NUMA core number 3 differs from configured core number 1
[    0.730856]  #14
[    0.743823] NUMA core number 3 differs from configured core number 1
[    0.752577]  #15
[    0.765253] NUMA core number 3 differs from configured core number 1
[    0.774002]  #16
[    0.786684] NUMA core number 3 differs from configured core number 1
[    0.795436]  #17
[    0.808113] NUMA core number 3 differs from configured core number 1
[    0.816878]  Ok.
[    0.819377] Booting Node   2, Processors  #18
[    0.834597] NUMA core number 2 differs from configured core number 1
[    0.843348]  #19
[    0.856025] NUMA core number 2 differs from configured core number 1
[    0.864777]  #20
[    0.877750] NUMA core number 2 differs from configured core number 1
[    0.886505]  #21
[    0.899180] NUMA core number 2 differs from configured core number 1
[    0.907939]  #22
[    0.920583] NUMA core number 2 differs from configured core number 1
[    0.929335]  #23 Ok.
[    0.942785] NUMA core number 2 differs from configured core number 1
[    0.951262] Brought up 24 CPUs

Thanks.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2012-04-04 12:38 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 [this message]
2012-04-16 17:31                     ` Borislav Petkov
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=20120404123809.GB5193@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=borislav.petkov@amd.com \
    --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 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.