From: Jon Smirl <jonsmirl@gmail.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Matthew Wilcox <willy@debian.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: multi-domain PCI and sysfs
Date: Sun, 5 Sep 2004 21:38:28 -0400 [thread overview]
Message-ID: <9e47339104090518387bdf2d0a@mail.gmail.com> (raw)
In-Reply-To: <200409051706.50455.jbarnes@engr.sgi.com>
Another way to look at this would be to create one vga device per
domain. I could then hook the vga=0/1 attribute off from this device
and avoid the problem of creating domain nodes under /sys/devices
On Sun, 5 Sep 2004 17:06:50 -0700, Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> On Sunday, September 5, 2004 4:04 pm, Matthew Wilcox wrote:
> > On Sat, Sep 04, 2004 at 04:03:56PM -0700, Jesse Barnes wrote:
> > > On Saturday, September 4, 2004 3:45 pm, Jon Smirl wrote:
> > > > Is this a multipath configuration where pci0000:01 and pci0000:02 can
> > > > both get to the same target bus? So both busses are top level busses?
> > > >
> > > > I'm trying to figure out where to stick the vga=0/1 attribute for
> > > > disabling all the VGA devices in a domain. It's starting to look like
> > > > there isn't a single node in sysfs that corresponds to a domain, in
> > > > this case there are two for the same domain.
> > >
> > > Yes, I think that's the case. Matthew would probably know for sure
> > > though.
> >
> > Huh, eh, what? There's no such thing as multipath PCI configurations.
> > The important concepts in PCI are:
>
> Right, but I was answering his question about whether or not there was a place
> to stick his 'vga' control file on a per-domain basis. There would be if the
> layout was something like this:
>
> /sys/devices/pciDDDD/BB/SS.F/foo
> rather than the current
> /sys/devices/pciDDDD:BB/DDDD:BB:SS.F/foo
>
> > I haven't really looked at the VGA attribute. I think Ivan or Grant
> > would be better equipped to help you on this front. I remember them
> > rehashing it 2-3 years ago.
>
> I'm actually ok with a system wide vga arbitration driver, assuming that we'll
> never have to worry about the scalability of stuff that wants to do legacy
> vga I/O.
>
> Thanks,
> Jesse
>
>
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2004-09-06 1:39 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
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 [this message]
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=9e47339104090518387bdf2d0a@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