From: Jon Smirl <jonsmirl@gmail.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: multi-domain PCI and sysfs
Date: Sat, 4 Sep 2004 18:45:23 -0400 [thread overview]
Message-ID: <9e47339104090415451c1f454f@mail.gmail.com> (raw)
In-Reply-To: <200409041527.50136.jbarnes@engr.sgi.com>
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.
On Sat, 4 Sep 2004 15:27:50 -0700, Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> On Saturday, September 4, 2004 3:12 pm, Jon Smirl wrote:
> > On Sat, 4 Sep 2004 14:57:46 -0700, Jesse Barnes <jbarnes@engr.sgi.com>
> wrote:
> > > Yep, on all the machines I've used.
> > >
> > > sn2 (ia64):
> > > [root@flatearth ~]# ls -l /sys/devices
> > > total 0
> > > drwxr-xr-x 5 root root 0 Sep 5 08:07 pci0000:01
> > > drwxr-xr-x 3 root root 0 Sep 5 08:07 pci0000:02
> > > drwxr-xr-x 2 root root 0 Sep 5 08:07 platform
> > > drwxr-xr-x 5 root root 0 Sep 5 08:07 system
> >
> > sn2 looks wrong. It should be
> >
> > > drwxr-xr-x 5 root root 0 Sep 5 08:07 pci0000:01
> > > drwxr-xr-x 3 root root 0 Sep 5 08:07 pci0001:02
> > > drwxr-xr-x 2 root root 0 Sep 5 08:07 platform
> > > drwxr-xr-x 5 root root 0 Sep 5 08:07 system
>
> It only has one domain though, so it's correct. Both busses are in domain 0.
>
> Jesse
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-04 22:45 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 [this message]
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
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=9e47339104090415451c1f454f@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.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