From: Matthew Wilcox <willy@debian.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@debian.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: pci_domain_nr vs. /sys/devices
Date: Wed, 11 Jun 2003 15:48:01 +0100 [thread overview]
Message-ID: <20030611144801.GZ28581@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1055341842.754.3.camel@gaston>
On Wed, Jun 11, 2003 at 04:30:42PM +0200, Benjamin Herrenschmidt wrote:
> The new pci_domain_nr() is good for adding the PCI domain number to
> the /sys/devices/pciN/* names, but I think that's not the proper
> representation. It should really be
>
> /sys/devices/pci-domainN/pciN/*
>
> So we can pave the way for when we'll stop play bus number tricks and
> actually have overlapping PCI bus numbers between domains. (I don't plan
> to do that immediately because that would break userland & /proc/bus/pci
> backward compatiblity)
>
> What do you think ?
I don't think sysfs works like that (please correct me if I've
misunderstood, mochel..)
Look in /sys/bus/pci/devices/ There you have all the PCI devices
lumped together in one place, and we obviously need the domain number
in the name. I don't know where the 0 on the end of /sys/devices/pci0/
comes from, but if we could, I wouldn't say no to:
/sys/devices/pciDDDD/DDDD:BB:SS.F
or
/sys/devices/pciDDDD:BB/DDDD:BB:SS.F
(Domain,Bus,Slot,Func)
I don't think the extra level of hierarchy in your suggestion is necessary
or particularly desirable.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-06-11 14:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:30 Benjamin Herrenschmidt
2003-06-11 14:48 ` Matthew Wilcox [this message]
2003-06-11 15:06 ` Benjamin Herrenschmidt
2003-06-11 15:12 ` Matthew Wilcox
2003-06-11 15:40 ` Russell King
2003-06-11 16:00 ` Benjamin Herrenschmidt
2003-06-17 4:52 ` Anton Blanchard
2003-06-11 17:03 ` Patrick Mochel
2003-06-17 4:49 ` Anton Blanchard
2003-06-17 9:41 ` Ivan Kokshaysky
2003-06-17 12:49 ` Anton Blanchard
2003-06-17 13:11 ` Ivan Kokshaysky
2003-06-17 19:42 ` Matthew Wilcox
2003-06-17 21:30 ` Ivan Kokshaysky
2003-06-18 13:02 ` Matthew Wilcox
2003-06-18 13:24 ` Ivan Kokshaysky
2003-06-17 13:55 ` Matthew Wilcox
2003-06-17 16:25 ` Matthew Wilcox
2003-06-17 18:39 ` Olaf Hering
2003-06-11 15:42 ` Russell King
2003-06-12 0:37 ` Anton Blanchard
2003-06-12 13:27 ` Benjamin Herrenschmidt
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=20030611144801.GZ28581@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/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
all inboxes | Powered by JetHome®