From: Jon Smirl <jonsmirl@gmail.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: multi-domain PCI and sysfs
Date: Tue, 7 Sep 2004 18:58:53 -0400 [thread overview]
Message-ID: <9e47339104090715585fa4f8af@mail.gmail.com> (raw)
In-Reply-To: <20040906014058.GV642@parcelfarce.linux.theplanet.co.uk>
On Mon, 6 Sep 2004 02:40:58 +0100, Matthew Wilcox <willy@debian.org> wrote:
> > When implementing the VGA control I'm running into the problem that
> > there is no root node in sysfs for the top of a domain. I need a
> > domain node to attach an attribute disabling all VGA devices in the
> > domain. In the zx1 diagram I could have vga devices on any of the
> > PCI-X or AGP buses.
>
> Why would it be a problem if the attribute is per-bus, as it is right now?
> see bus->bridge_ctl (PCI_BRIDGE_CTL_VGA)
>
> Actually, they're sparsely numbered to allow for people plugging in pci-pci
> bridges on cards, so:
>
> $ ls -1 /sys/devices/
> pci0000:00
> pci0000:80
> pci0000:a0
> pci0000:c0
> platform
> system
How many active VGA devices can I have in this system 1 or 4? If the
answer is 4, how do I independently address each VGA card? If the
answer is one, you can see why I want a pci0000 node to hold the
attribute for turning it off and on.
How many simultaneous VGA devices does this system allow?
ppc32:
jbarnes@mill:~$ ls -l /sys/devices
total 0
drwxr-xr-x 5 root root 0 Sep 4 13:37 pci0000:00/
drwxr-xr-x 13 root root 0 Sep 4 13:37 pci0001:01/
drwxr-xr-x 7 root root 0 Sep 4 13:37 pci0002:06/
drwxr-xr-x 3 root root 0 Sep 4 13:37 platform/
drwxr-xr-x 4 root root 0 Sep 4 13:37 system/
drwxr-xr-x 5 root root 0 Sep 4 13:37 uni-n-i2c/
I would think it is three active devices.
Does a PCI domain imply separate PCI IO address spaces, or does it
just mean separate PCI Config spaces?
Can an x86 machine use separate PCI IO address spaces?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-07 23:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 20:00 multi-domain PCI and sysfs Jon Smirl
2004-09-04 21:57 ` Jesse Barnes
2004-09-04 22:12 ` Jon Smirl
2004-09-04 22:27 ` Jesse Barnes
2004-09-04 22:45 ` Jon Smirl
2004-09-04 23:03 ` Jesse Barnes
2004-09-05 23:04 ` Matthew Wilcox
2004-09-05 23:50 ` Jon Smirl
2004-09-05 23:00 ` Alan Cox
2004-09-06 1:40 ` Matthew Wilcox
2004-09-07 22:58 ` Jon Smirl [this message]
2004-09-07 23:11 ` David S. Miller
2004-09-08 3:39 ` Jon Smirl
2004-09-08 4:12 ` David S. Miller
2004-09-08 4:16 ` Jesse Barnes
2004-09-08 4:15 ` Jesse Barnes
2004-09-08 4:16 ` David S. Miller
2004-09-08 4:25 ` Jesse Barnes
2004-09-08 6:01 ` Jon Smirl
2004-09-08 13:02 ` Alan Cox
2004-09-08 16:02 ` Jesse Barnes
2004-09-08 18:20 ` David S. Miller
2004-09-08 18:32 ` Jesse Barnes
2004-09-08 18:54 ` David S. Miller
2004-09-08 6:55 ` Jon Smirl
2004-09-08 11:11 ` Geert Uytterhoeven
2004-09-08 11:38 ` Matthew Wilcox
2004-09-08 18:21 ` David S. Miller
2004-09-08 22:41 ` Alan Cox
2004-09-09 0:31 ` Jon Smirl
2004-09-09 13:06 ` Alan Cox
2004-09-08 15:03 ` Matthew Wilcox
2004-09-06 0:06 ` Jesse Barnes
2004-09-06 0:31 ` Jon Smirl
2004-09-06 1:38 ` Jon Smirl
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=9e47339104090715585fa4f8af@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.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