From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Francisco Jesús Martínez Serrano" <franjesus@gmail.com>
Cc: "Andre Przywara" <andre.przywara@amd.com>,
discuss@x86-64.org, "Andi Kleen" <ak@suse.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [discuss] Weird cpu mapping on 8-way dual-core machine
Date: Tue, 26 Feb 2008 22:21:31 -0800 [thread overview]
Message-ID: <86802c440802262221x66f2ccf8s2f290efd184891dd@mail.gmail.com> (raw)
In-Reply-To: <86802c440802262148p7cee20bft8a00d14ba8ae1470@mail.gmail.com>
On Tue, Feb 26, 2008 at 9:48 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Tue, Feb 26, 2008 at 9:58 AM, Francisco Jesús Martínez Serrano
> <franjesus@gmail.com> wrote:
> > 2008/2/26, Andre Przywara:
> >
> > > So your BIOS option disables the shifting workaround and everything
> > > works as intended by the specification, although I am not sure whether
> > > you have any side effects (see above).
> >
> > Maybe I'm getting some side effects, but I'm not sure, when running an
> > OpenMP code, I get a lot of numa_misses, at node1 and the same number
> > of numa_foreign at node0.
> >
> > Out of pure ignorance, I was wondering if it could be related to the
> > node0 getting 505896 pages (I believe that's 1976.2 MB) of
> > ZONE_DMA32. I've seen options to disable DMA and DMA32. Is it safe?
> >
> can you try x86.git#testing ?
>
> http://people.redhat.com/mingo/x86.git/README
>
> and connect with serial console.
>
> command line:
> apic=debug acpi.debug_level=0x0000000F debug console=uart8250,io,0x3f8,115200n8
>
core fix is in x86.git#testing
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-x86.git;a=commitdiff;h=ae2627a87c6f186ced0539d8e6f7a2c78dabc4c5
it will make sure that apicid to node mapping is right.
esp don't have SRAT or wrong SRAT, and your system have apicid lifting
YH
parent reply other threads:[~2008-02-27 6:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86802c440802262148p7cee20bft8a00d14ba8ae1470@mail.gmail.com>]
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=86802c440802262221x66f2ccf8s2f290efd184891dd@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ak@suse.de \
--cc=andre.przywara@amd.com \
--cc=discuss@x86-64.org \
--cc=franjesus@gmail.com \
--cc=linux-kernel@vger.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®