From: Andreas Herrmann <herrmann.der.user@googlemail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: Re: x86, amd: Get multi-node CPU info from NodeId MSR instead of PCI config space
Date: Fri, 16 Oct 2009 14:57:00 +0200 [thread overview]
Message-ID: <20091016125700.GD8387@alberich.amd.com> (raw)
In-Reply-To: <20091016123853.GA15393@elte.hu>
On Fri, Oct 16, 2009 at 02:38:53PM +0200, Ingo Molnar wrote:
>
> * Andreas Herrmann <herrmann.der.user@googlemail.com> wrote:
>
> > Use newly introduced NodeId MSR to get NodeId and number of nodes per
> > processor.
>
> What will happen on CPUs that dont have this MSR and got this info from
> the PCI config space:
No PCI config space needed as all Magny-Cours CPUs should support this
when launched.
> > static void __cpuinit amd_fixup_dcm(struct cpuinfo_x86 *c)
> > {
> > -#ifdef CONFIG_PCI
> > - u32 t, cpn;
> > - u8 n, n_id;
> > int cpu = smp_processor_id();
> >
> > /* fixup topology information only once for a core */
> > if (cpu_has(c, X86_FEATURE_AMD_DCM))
> > return;
> >
> > - /* check for multi-node processor on boot cpu */
> > - t = read_pci_config(0, 24, 3, 0xe8);
> > - if (!(t & (1 << 29)))
> > return;
> >
> > set_cpu_cap(c, X86_FEATURE_AMD_DCM);
>
> are there any such CPUs?
Only Magny-Cours so far.
> I.e. we want to know the effect of this patch
> on various models of AMD CPUs - is the change really .32 safe? Does it
> solve any problem that makes it .32 material versus being for .33?
IMHO getting rid of the PCI config space accesses as soon as possible
is a benefit, I think.
Andreas
next prev parent reply other threads:[~2009-10-16 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 12:22 x86, amd: Get multi-node CPU info from NodeId MSR instead of PCI config space Andreas Herrmann
2009-10-16 12:38 ` Ingo Molnar
2009-10-16 12:57 ` Andreas Herrmann [this message]
2009-10-16 13:00 ` Ingo Molnar
2009-10-16 13:05 ` Andreas Herrmann
2009-10-27 9:33 ` [PATCH RESEND] " 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=20091016125700.GD8387@alberich.amd.com \
--to=herrmann.der.user@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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