public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Patrick Mochel <mochel@osdl.org>
Subject: Re: pci_domain_nr vs. /sys/devices
Date: 11 Jun 2003 17:06:20 +0200	[thread overview]
Message-ID: <1055343980.755.7.camel@gaston> (raw)
In-Reply-To: <20030611144801.GZ28581@parcelfarce.linux.theplanet.co.uk>

On Wed, 2003-06-11 at 16:48, Matthew Wilcox wrote:

> I don't think sysfs works like that (please correct me if I've
> misunderstood, mochel..)

Looks like nobody really understands it then ;)

> 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:

Nah, you are mixing up /sys/bus/* which is a flat list of busses in the
machine, with /sys/devices/* which is the hierarchical device tree.

> I don't think the extra level of hierarchy in your suggestion is necessary
> or particularly desirable.

It's probably not, then it's a matter of properly renaming the pciN entries
in /sys/devices to be /sys/devices/pciDD:NN where DD is the domain number
and NN is the first bus on this domain, or just pciDD (though I like having
the bus number there as well)

Ben.




  reply	other threads:[~2003-06-11 14:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 14:30 pci_domain_nr vs. /sys/devices Benjamin Herrenschmidt
2003-06-11 14:48 ` Matthew Wilcox
2003-06-11 15:06   ` Benjamin Herrenschmidt [this message]
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=1055343980.755.7.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=willy@debian.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