From: Borislav Petkov <bp@amd64.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Borislav Petkov <bp@amd64.org>, Ingo Molnar <mingo@kernel.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 15:37:22 +0200 [thread overview]
Message-ID: <20120604133722.GB15433@aftab.osrc.amd.com> (raw)
In-Reply-To: <1338813830.28282.44.camel@twins>
On Mon, Jun 04, 2012 at 02:43:50PM +0200, Peter Zijlstra wrote:
> On Mon, 2012-06-04 at 14:41 +0200, Borislav Petkov wrote:
> > The warning below triggers on AMD MCM packages because physical
> > package
> > IDs on the cores of a _physical_ socket are the same. I.e., this field
> > says which CPUs belong to the same physical package.
> >
> Thanks!
This is still crap.
It breaks tests like those in powernow-k8:
if (cpumask_first(cpu_core_mask(data->cpu)) == data->cpu)
print_basics(data);
and it calls print_basics() on each core filling up dmesg with:
[ 5.216925] powernow-k8: 0 : pstate 0 (1700 MHz)
[ 5.222139] powernow-k8: 1 : pstate 1 (1300 MHz)
[ 5.227354] powernow-k8: 2 : pstate 2 (1100 MHz)
[ 5.232568] powernow-k8: 3 : pstate 3 (1000 MHz)
[ 5.237783] powernow-k8: 4 : pstate 4 (800 MHz)
[ 5.242988] powernow-k8: 0 : pstate 0 (1700 MHz)
[ 5.248242] powernow-k8: 1 : pstate 1 (1300 MHz)
[ 5.253462] powernow-k8: 2 : pstate 2 (1100 MHz)
[ 5.258677] powernow-k8: 3 : pstate 3 (1000 MHz)
[ 5.263892] powernow-k8: 4 : pstate 4 (800 MHz)
[ 5.269094] powernow-k8: 0 : pstate 0 (1700 MHz)
[ 5.274348] powernow-k8: 1 : pstate 1 (1300 MHz)
[ 5.279566] powernow-k8: 2 : pstate 2 (1100 MHz)
[ 5.284787] powernow-k8: 3 : pstate 3 (1000 MHz)
[ 5.298387] powernow-k8: 4 : pstate 4 (800 MHz)
...
while it should dump the Pstates only once per physical socket.
The proper fix should be:
static bool __cpuinit match_mc(struct cpuinfo_x86 *c, struct cpuinfo_x86 *o)
{
if (c->phys_proc_id == o->phys_proc_id) {
if (cpu_has(c, X86_FEATURE_AMD_DCM))
return true;
return topology_sane(c, o, "mc");
}
return false;
}
which basically circumvents the topology check on MCM modules. I'll run
this a bit longer to verify it doesn't break anything else.
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-06-04 13:36 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 [this message]
2012-06-04 13:38 ` Peter Zijlstra
2012-06-04 14:48 ` Borislav Petkov
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=20120604133722.GB15433@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andreas.herrmann3@amd.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
all inboxes | Powered by JetHome®