All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>,
	bcollins@debian.org, wli@holomorphy.com, tom_gall@vnet.ibm.com,
	Anton Blanchard <anton@samba.org>
Subject: Re: /proc/bus/pci
Date: 05 Jun 2003 14:43:16 +0200	[thread overview]
Message-ID: <1054816995.1000.6.camel@gaston> (raw)
In-Reply-To: <1054814759.22103.6114.camel@cube>


> So sysfs then has:
> 
> devices/pci2/02:0b.0 -> ../hose0/bus2/dev11/fn0
> devices/hose0/bus2/dev11/fn0/config-space
> devices/hose0/bus2/dev11/fn0/bar0
> devices/hose0/bus2/dev11/fn0/bar1
> devices/hose0/bus2/dev11/fn0/bar2
> devices/hose0/bus2/dev11/fn0/class
> devices/hose0/bus2/dev11/fn0/power
> devices/hose0/bus2/dev11/fn0/subsystem_vendor
> devices/hose0/bus2/dev11/fn0/and-so-on

The first entry (devices/pci2/....) is wrong imho.

With multiple domains, we can have several busses with the same bus number,
one in each domain. So it's a matter of taking the current set of pciN
entries and moving them below a "pci-domain" entry (or hose, or whatever
Linus prefers).

Also, the node name for individual PCI devices must include the domain
number, the current bus:dev.fn notation isn't enough, that will break
things like /sys/bus/pci/devices when you have several identical bus/devfn
pairs on different domains

Ben.


  parent reply	other threads:[~2003-06-05 12:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  3:21 /proc/bus/pci Albert Cahalan
2003-06-05  3:35 ` /proc/bus/pci William Lee Irwin III
2003-06-05  4:23 ` /proc/bus/pci Linus Torvalds
2003-06-05  5:01   ` /proc/bus/pci David S. Miller
2003-06-05 12:05   ` /proc/bus/pci Albert Cahalan
2003-06-05 12:16     ` /proc/bus/pci David S. Miller
2003-06-05 12:42       ` /proc/bus/pci Albert Cahalan
2003-06-05 12:36     ` /proc/bus/pci Albert Cahalan
2003-06-05 15:51       ` /proc/bus/pci Linus Torvalds
2003-06-05 16:00         ` /proc/bus/pci William Lee Irwin III
2003-06-05 17:23           ` /proc/bus/pci Benjamin Herrenschmidt
2003-06-05 17:36             ` /proc/bus/pci William Lee Irwin III
2003-06-05 17:18         ` /proc/bus/pci Riley Williams
2003-06-06 16:30         ` /proc/bus/pci Ross Biro
2003-06-06 18:13           ` /proc/bus/pci Riley Williams
2003-06-07  2:02           ` /proc/bus/pci Horst von Brand
2003-06-07  0:25         ` /proc/bus/pci Robert White
2003-06-07  0:35           ` /proc/bus/pci Linus Torvalds
2003-06-07  1:01             ` /proc/bus/pci Robert White
2003-06-07  1:43             ` /proc/bus/pci Albert Cahalan
2003-06-05 12:43     ` Benjamin Herrenschmidt [this message]
2003-06-05 16:58 ` /proc/bus/pci Greg KH
2003-06-05 18:27   ` /proc/bus/pci Matt Wilson
2003-06-05 19:35     ` /proc/bus/pci Greg KH
     [not found] <20030605125013$41ac@gated-at.bofh.it>
     [not found] ` <20030605160017$10e1@gated-at.bofh.it>
2003-06-05 16:41   ` /proc/bus/pci Julien Oster
2003-06-05 16:57     ` /proc/bus/pci Mike Dresser
2003-06-05 17:00     ` /proc/bus/pci Richard B. Johnson
2003-06-07  0:31       ` /proc/bus/pci Robert White
2003-06-05 20:49     ` /proc/bus/pci Michal Jaegermann
2003-06-12  4:29       ` /proc/bus/pci Andre Hedrick
2003-06-13  7:10         ` /proc/bus/pci Riley Williams
2003-06-13  8:43           ` /proc/bus/pci Olivier Galibert
2003-06-13 16:28           ` /proc/bus/pci Mr. James W. Laferriere
2003-06-13 17:59             ` /proc/bus/pci Riley Williams
2003-06-13 19:37               ` /proc/bus/pci Mr. James W. Laferriere
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 17:03 /proc/bus/pci Grover, Andrew

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=1054816995.1000.6.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=albert@users.sourceforge.net \
    --cc=anton@samba.org \
    --cc=bcollins@debian.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom_gall@vnet.ibm.com \
    --cc=torvalds@transmeta.com \
    --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.