From: Brice Goglin <Brice.Goglin@inria.fr>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
Paul Mundt <lethal@linux-sh.org>, Chris Snook <csnook@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Purpose of numa_node?
Date: Thu, 31 Jan 2008 22:35:24 +0100 [thread overview]
Message-ID: <47A23F1C.7080809@inria.fr> (raw)
In-Reply-To: <86802c440801311329h67a79139xa33994e2cc116781@mail.gmail.com>
Yinghai Lu wrote:
> On Jan 31, 2008 5:42 AM, Brice Goglin <Brice.Goglin@inria.fr> wrote:
>
>> It works fine on regular machines such as dual opterons. However, I
>> noticed recently that it was wrong on some quad-opteron machines (see
>> http://marc.info/?l=linux-pci&m=119072400008538&w=2) because something
>> is not initialized in the right order. But I haven't tested 2.6.24 on
>> this hardware yet, and I don't know if things have changed regarding this.
>>
>
> that will depend if you dsdt have _PXM for your pci root bus.
> otherwise you will get all -1
>
Have a look at the above link. I don't get -1. I get 0 everywhere, while
I should get 1 for some devices. And if I unplug/replug a device using
fakephp, numa_node becomes correct (1 instead of 0). This just looks
like the code is there but things are initialized in the wrong order.
Brice
next prev parent reply other threads:[~2008-01-31 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 0:48 Purpose of numa_node? Chris Snook
2008-01-31 7:40 ` Paul Mundt
2008-01-31 9:56 ` Andi Kleen
2008-01-31 13:42 ` Brice Goglin
2008-01-31 21:29 ` Yinghai Lu
2008-01-31 21:35 ` Brice Goglin [this message]
2008-01-31 21:42 ` Yinghai Lu
2008-01-31 23:35 ` Yinghai Lu
2008-02-13 18:52 ` Brice Goglin
2008-02-13 21:31 ` Yinghai Lu
2008-02-20 21:55 ` Yinghai Lu
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=47A23F1C.7080809@inria.fr \
--to=brice.goglin@inria.fr \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=csnook@redhat.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.com \
/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