[lkml]   [2003]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: /proc/bus/pci
    On Wed, Jun 04, 2003 at 11:21:43PM -0400, Albert Cahalan wrote:
    > I notice that /proc/bus/pci doesn't offer a sane
    > interface for multiple PCI domains and choice of BAR.
    > What do people think of this?
    > bus/pci/00/00.0 -> ../hose0/bus0/dev0/fn0/config-space
    > bus/pci/hose0/bus0/dev0/fn0/config-space
    > bus/pci/hose0/bus0/dev0/fn0/bar0
    > bus/pci/hose0/bus0/dev0/fn0/bar1
    > bus/pci/hose0/bus0/dev0/fn0/bar2
    > bus/pci/hose0/bus0/dev0/fn0/status
    > Then with some mmap flags, the nasty ioctl() stuff
    > won't be needed anymore. It can die during 2.7.xx
    > development. If MAP_MMIO isn't generally acceptable,
    > then it could be via filename suffixes. (eeew, IMHO)
    > One remaining problem is permission. Any complaints
    > about implementing chmod() for those? Since this
    > does bypass capabilities, a mount option might be
    > used to enable it.
    > As alternatives to /proc changes, a distinct filesystem
    > could be developed or sysfs could be abused.

    Matt Wilson and I have been talking about some changes like this
    recently. This was because some of the ppc64 ports are doing some other
    weird things to try to handle the bigger IBM machines (they were abusing
    the pci structures pretty badly, not pretty stuff.)

    We agreed that we should call this a "domain", too, and he has a patch
    that he says works for X.

    Hopefully this prod will get him to send out his patch :)


    greg k-h
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:36    [W:14.876 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site