Messages in this thread | | | Date | Wed, 11 Jun 2003 15:48:01 +0100 | From | Matthew Wilcox <> | Subject | Re: pci_domain_nr vs. /sys/devices |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |