lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440801311535v2bb9977ma884129662c9a2d5@mail.gmail.com>
Date:	Thu, 31 Jan 2008 15:35:12 -0800
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Brice Goglin" <Brice.Goglin@...ia.fr>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Andi Kleen" <ak@...e.de>, "Ingo Molnar" <mingo@...e.hu>,
	"Paul Mundt" <lethal@...ux-sh.org>,
	"Chris Snook" <csnook@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Purpose of numa_node?

On Jan 31, 2008 1:42 PM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
>
> On Jan 31, 2008 1:35 PM, Brice Goglin <Brice.Goglin@...ia.fr> wrote:
> > Yinghai Lu wrote:
> > > On Jan 31, 2008 5:42 AM, Brice Goglin <Brice.Goglin@...ia.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.
>
> do you have
> ...
> bus 00 -> pxm 0 -> node 0
> ...
> bus 40 -> pxm 1 -> node 1
> ...
> bus 80 -> pxm 1 -> node 1
>
> in your boot msg or dmesg?
>
> if not, your dsdt doesn't have _PXM for pci root bus. or you need to
> ask your HW vendor to add that in their BIOS, or use my patchset.

please try the attached patchset

please get x86.git then use quilt apply the patch

http://people.redhat.com/mingo/x86.git/README

YH

Download attachment "patches_01312008_mm_bus_numa.tar.bz2" of type "application/x-bzip2" (12361 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ