From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Borislav Petkov <bp@amd64.org>
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, hpa <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: WARNING: at arch/x86/kernel/smpboot.c:310 topology_sane.clone.1+0x6e/0x81()
Date: Tue, 29 May 2012 19:25:19 +0200 [thread overview]
Message-ID: <1338312319.26856.159.camel@twins> (raw)
In-Reply-To: <20120529171305.GK29157@aftab.osrc.amd.com>
On Tue, 2012-05-29 at 19:13 +0200, Borislav Petkov wrote:
>
> > As it stands I think we should discuss the definition for the generic
> > topology bits (drivers/base/topology.c), because I think your
> > Magny-Cours thing does the wrong thing here.
>
> "wrong" is such a strong word :-) Please elaborate and I'll have a look.
Right, so I meant LLC is the useful mask, and in my mind LLC is what
makes a multi-core, without shared cache its just SMP. So core_siblings
to me would mean LLC sharing cores.
But its all very subjective I guess, but using strong words gets the
discussion going better ;-)
> > The core span in a phys_id is all nice and such, but what does it mean?
>
> AFAICT, this is the physical package id to which the cores belong, i.e.
> physical socket.
>
> > IOW what would you do with it?
>
> Shoot empty cans with it... :-)
Right, I actually came up with proper use-case, physical hotplug :-)
Its not immediately obvious the sysfs topo bits have the llc mask, which
is the more 'useful' one IMO.
Another funny case I don't see represented well is where there's
multiple sockets to a node -- I know this is like ancient tech and
unlikely in these days of multi-node sockets, but still ;-)
I guess what I'm asking is what is the purpose of the sys topo bits?
next prev parent reply other threads:[~2012-05-29 17:25 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 [this message]
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
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=1338312319.26856.159.camel@twins \
--to=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=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