From: Jeff Garzik <jeff@garzik.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
riku.seppala@kymp.net, Andy Whitcroft <apw@shadowen.org>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFT] finish i386 and x86-64 sysdata conversion
Date: Tue, 07 Aug 2007 21:21:24 -0400 [thread overview]
Message-ID: <46B91A94.7000509@garzik.org> (raw)
In-Reply-To: <86802c440708071809g7a204200lde6f027a1bf496e9@mail.gmail.com>
Yinghai Lu wrote:
> the sysdata stuff try to fix:
> when calgary iommu code was introduced, it is trying to share sysdata
> that orginally is initialized k8_bus.c and used by pcibus_to_node. but
> that only happen with AMD K8 platform. and have nothing to do with
> calgary.
incorrect: sysdata is initialized when the structure is created, which
clearly not only in k8_bus.c
> Then my patch get_mp_bus_to_node_as_early will use that sysdata as
> node as early as possible before the pci_scan bus is called.
that's incorrect, since it assumes NUMA owns ->sysdata
> then Mul came out his patch ...to split the sharing that will never happen.
that's incorrect, ->sysdata will be shared among Calgary, NUMA, and
PCI-domain support.
> Also i don't think anyone test muli sysdata patch with amd64 platform
> with acpi=off. even muli himself.
I did. I did all PCI domain support development on AMD64 platform.
> calgary support bus numa at this time? i mean mult peer root bus on
> different node..
My PCI domains patch add support for multiple peer root buses. That's
the definition of PCI domain support.
Branch 'pciseg' of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
Jeff
next prev parent reply other threads:[~2007-08-08 1:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 22:10 Oops in 2.6.23-rc1-git9, arch/x86_64/pci/k8-bus.c::fill_mp_bus_to_cpumask() Chuck Ebbert
2007-08-03 22:50 ` Andrew Morton
2007-08-04 6:17 ` Muli Ben-Yehuda
2007-08-04 9:30 ` Andi Kleen
2007-08-04 16:32 ` Andrew Morton
2007-08-04 17:45 ` Yinghai Lu
2007-08-04 18:15 ` Andrew Morton
2007-08-04 19:02 ` Yinghai Lu
2007-08-05 5:52 ` Andrew Morton
2007-08-05 6:02 ` Muli Ben-Yehuda
2007-08-05 6:07 ` Yinghai Lu
2007-08-05 6:11 ` Muli Ben-Yehuda
2007-08-05 6:24 ` Yinghai Lu
2007-08-05 6:27 ` Yinghai Lu
2007-08-05 6:04 ` Yinghai Lu
2007-08-04 23:40 ` Andi Kleen
2007-08-05 4:15 ` Muli Ben-Yehuda
2007-08-05 4:33 ` Yinghai Lu
2007-08-05 5:00 ` Muli Ben-Yehuda
2007-08-05 4:31 ` Yinghai Lu
2007-08-05 5:04 ` Muli Ben-Yehuda
2007-08-05 5:38 ` Yinghai Lu
2007-08-05 7:53 ` [PATCH/RFT] finish i386 and x86-64 sysdata conversion Muli Ben-Yehuda
2007-08-05 8:49 ` Yinghai Lu
2007-08-05 11:54 ` Muli Ben-Yehuda
2007-08-05 16:39 ` Yinghai Lu
2007-08-05 17:36 ` Jeff Garzik
2007-08-05 20:41 ` Yinghai Lu
2007-08-07 22:49 ` Andrew Morton
2007-08-07 22:56 ` Muli Ben-Yehuda
2007-08-08 0:43 ` Jeff Garzik
2007-08-08 1:09 ` Yinghai Lu
2007-08-08 1:21 ` Jeff Garzik [this message]
2007-08-08 1:28 ` Yinghai Lu
2007-08-08 2:59 ` 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=46B91A94.7000509@garzik.org \
--to=jeff@garzik.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=riku.seppala@kymp.net \
--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