From: Anton Blanchard <anton@samba.org>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: 48GB NUMA-Q boots, with major IO-APIC hassles
Date: Wed, 15 Jan 2003 22:24:12 +1100 [thread overview]
Message-ID: <20030115112412.GA5062@krispykreme> (raw)
In-Reply-To: <20030115105802.GQ940@holomorphy.com>
> -- I've already tried and failed on PCI segments.
> -- I would be much obliged for advice on this one, especially
> -- since the workaround cripples the machine.
I was wondering if we could use pci_scan_bus_parented as a start.
Assuming we fixed pci_bus_exists, this should allow us to create
overlapping busses.
What else needs fixing? To start with:
* pci config read/writes
Should be arch specific, can hide things in struct pci_bus
which is passed in. (eg on ppc64 we have to pass an identifier
into the low level config read or write)
* pci IO/memory reads/writes
No problems on ppc64, it should just work. Are there problems
on x86?
* /proc/bus/pci/
As davem pointed out we have a backwards compatibility bit
where all devices on domain 0 appear as they always have.
Additionally we create another level of directories to represent
the domain.
* /proc/pci
Need to print the domain
* device printing
We need a macro that drivers can use to print their PCI location
Then we make that print the domain.
* sysfs
I havent looked into this yet
Does anything else spring to mind?
Anton
next prev parent reply other threads:[~2003-01-15 11:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:58 48GB NUMA-Q boots, with major IO-APIC hassles William Lee Irwin III
2003-01-15 10:58 ` William Lee Irwin III
2003-01-15 11:24 ` Anton Blanchard [this message]
2003-01-15 11:55 ` William Lee Irwin III
2003-01-15 12:32 ` Anton Blanchard
2003-01-15 13:10 ` William Lee Irwin III
2003-01-15 15:24 ` Martin J. Bligh
2003-01-15 15:24 ` Martin J. Bligh
2003-01-15 15:34 ` William Lee Irwin III
2003-01-15 15:34 ` William Lee Irwin III
2003-01-19 1:43 ` William Lee Irwin III
2003-01-19 1:50 ` William Lee Irwin III
2003-01-19 2:13 ` Zwane Mwaikambo
2003-01-19 2:27 ` William Lee Irwin III
2003-01-19 2:32 ` Zwane Mwaikambo
2003-01-19 2:55 ` William Lee Irwin III
2003-01-19 3:08 ` William Lee Irwin III
2003-03-28 5:08 ` William Lee Irwin III
2003-03-28 5:08 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 17:32 Protasevich, Natalie
2003-01-15 22:01 ` Martin J. Bligh
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=20030115112412.GA5062@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.