From: Andi Kleen <andi@firstfloor.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Joachim Deguara <joachim.deguara@amd.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, Dean Roe <roe@cray.com>
Subject: Re: [PATCH] x86: add PCI IDs to k8topology_64.c II
Date: Tue, 29 Jan 2008 09:31:12 +0100 [thread overview]
Message-ID: <20080129083112.GA1466@one.firstfloor.org> (raw)
In-Reply-To: <86802c440801282339q77a585f5h82df44295ddfb6fd@mail.gmail.com>
On Mon, Jan 28, 2008 at 11:39:30PM -0800, Yinghai Lu wrote:
> On Jan 29, 2008 12:09 AM, Andi Kleen <andi@firstfloor.org> wrote:
> > > SRAT is essentially just a two dimensional table with node distances.
> >
> > Sorry, that was actually SLIT. SRAT is not two dimensional, but also
> > relatively simple. SLIT you don't really need to implement.
> >
>
> need to add some CONFIG option to parse SRAT, MADT etc only. but don't
> pull DSDT related...
I don't think it needs a CONFIG. The code should handle this case
by itself in any case. I'm not entirely sure it does currently, but if it
doesn't it will likely not be very difficult to fix.
Or are you worried about code size? ACPI is around ~270k on x86-64,
which while certainly not small should not be a problem on x86 NUMA
systems.
-Andi
next prev parent reply other threads:[~2008-01-29 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 20:11 [PATCH] x86: add PCI IDs to k8topology_64.c Joachim Deguara
2008-01-28 20:54 ` Ingo Molnar
2008-01-28 21:49 ` Yinghai Lu
2008-01-29 3:48 ` Andi Kleen
2008-01-29 4:12 ` Yinghai Lu
2008-01-29 4:56 ` Andi Kleen
2008-01-29 6:03 ` H. Peter Anvin
2008-01-29 8:09 ` [PATCH] x86: add PCI IDs to k8topology_64.c II Andi Kleen
2008-01-29 7:39 ` Yinghai Lu
2008-01-29 8:31 ` Andi Kleen [this message]
2008-01-29 8:20 ` Yinghai Lu
2008-02-01 15:58 ` dean gaudet
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=20080129083112.GA1466@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=joachim.deguara@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roe@cray.com \
--cc=tglx@linutronix.de \
--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