From: Borislav Petkov <borislav.petkov@amd.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Cc: Borislav Petkov <bp@amd64.org>, X86-ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: [PATCH] x86, smp: Fix topology checks on AMD MCM
Date: Mon, 4 Jun 2012 16:48:50 +0200 [thread overview]
Message-ID: <20120604144850.GF15433@aftab.osrc.amd.com> (raw)
In-Reply-To: <1338817117.28282.48.camel@twins>
On Mon, Jun 04, 2012 at 03:38:37PM +0200, Peter Zijlstra wrote:
> On Mon, 2012-06-04 at 15:37 +0200, Borislav Petkov wrote:
> > This is still crap.
>
> *poof* and the patch is gone.. I'll wait for an update ;-)
Thanks.
So I'm looking more into this and there's another issue IMHO:
processor : 2
vendor_id : AuthenticAMD
cpu family : 16
model : 9
stepping : 1
microcode : 0x10000d9
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings : 12
core id : 2
cpu cores : 2
^^^^^^^^^^^^^^^^^^^
This is cpuinfo_x86.booted_cores and here's how it progresses on this
MCM box (below).
On core 2 it becomes 2 and it doesn't change again. Until the next
physical socket comes (cpu 12) where it starts again from 1.
And, it is normally the number of booted cores on the socket, i.e. 12 in
this case.
Now, before we go babbling about what the right fix is, maybe we should
remove this thing completely - I mean, it looks like no one uses it, it
is only in the /proc/cpuinfo thing. Ingo, hpa?
$ grep -E "(cpu cores|processor)" /proc/cpuinfo
processor : 0
cpu cores : 1
processor : 1
cpu cores : 2
processor : 2
cpu cores : 2
processor : 3
cpu cores : 2
processor : 4
cpu cores : 2
processor : 5
cpu cores : 2
processor : 6
cpu cores : 2
processor : 7
cpu cores : 2
processor : 8
cpu cores : 2
processor : 9
cpu cores : 2
processor : 10
cpu cores : 2
processor : 11
cpu cores : 2
processor : 12
cpu cores : 1
processor : 13
cpu cores : 2
processor : 14
cpu cores : 2
processor : 15
cpu cores : 2
processor : 16
cpu cores : 2
processor : 17
cpu cores : 2
processor : 18
cpu cores : 2
processor : 19
cpu cores : 2
processor : 20
cpu cores : 2
processor : 21
cpu cores : 2
processor : 22
cpu cores : 2
processor : 23
cpu cores : 2
--
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-06-04 14:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 13:54 WARNING: at arch/x86/kernel/smpboot.c:310 topology_sane.clone.1+0x6e/0x81() Borislav Petkov
2012-05-29 14:51 ` Peter Zijlstra
2012-05-29 15:29 ` Andreas Herrmann
2012-05-29 16:59 ` Peter Zijlstra
2012-05-29 17:13 ` Borislav Petkov
2012-05-29 17:25 ` Peter Zijlstra
2012-05-29 17:48 ` Andreas Herrmann
2012-06-04 12:41 ` [PATCH] x86, smp: Fix topology checks on AMD MCM Borislav Petkov
2012-06-04 12:43 ` Peter Zijlstra
2012-06-04 13:37 ` Borislav Petkov
2012-06-04 13:38 ` Peter Zijlstra
2012-06-04 14:48 ` Borislav Petkov [this message]
2012-06-04 14:56 ` Peter Zijlstra
2012-06-04 16:01 ` Borislav Petkov
2012-06-06 15:31 ` [PATCH -v2] " Borislav Petkov
2012-06-14 8:39 ` [tip:x86/urgent] x86/smp: Fix topology checks on AMD MCM CPUs tip-bot for Borislav Petkov
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=20120604144850.GF15433@aftab.osrc.amd.com \
--to=borislav.petkov@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andreas.herrmann3@amd.com \
--cc=bp@amd64.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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