From: "David S. Miller" <davem@redhat.com>
To: ink@jurassic.park.msu.ru
Cc: jgarzik@mandrakesoft.com, andrew.grover@intel.com,
mochel@osdl.org, Greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: pci segments/domains
Date: Fri, 17 May 2002 05:15:18 -0700 (PDT) [thread overview]
Message-ID: <20020517.051518.35579118.davem@redhat.com> (raw)
In-Reply-To: <20020517162621.A24213@jurassic.park.msu.ru>
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Date: Fri, 17 May 2002 16:26:21 +0400
BTW, I don't see anymore why pci domain info should be exposed to
users at all. :-)
It allows the X server do what it wants to sort-of sanely.
It wants to be able to assign resources to video devices (even
implicit resources like VGA) and to do that properly it has to know
which PCI domain which devices are on and also the extent of the I/O
and MEM space on that domain.
next prev parent reply other threads:[~2002-05-17 12:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 2:07 pci segments/domains Grover, Andrew
2002-05-14 2:08 ` David S. Miller
2002-05-16 19:33 ` Jeff Garzik
2002-05-17 1:31 ` David S. Miller
2002-05-16 23:10 ` Pavel Machek
2002-05-17 10:47 ` Ivan Kokshaysky
2002-05-17 10:40 ` David S. Miller
2002-05-17 11:11 ` Ivan Kokshaysky
2002-05-17 11:04 ` David S. Miller
2002-05-17 11:39 ` Ivan Kokshaysky
2002-05-17 11:41 ` David S. Miller
2002-05-17 12:26 ` Ivan Kokshaysky
2002-05-17 12:15 ` David S. Miller [this message]
2002-05-17 14:24 ` Jeff Garzik
2002-05-17 14:16 ` David S. Miller
2002-05-17 14:33 ` Jeff Garzik
2002-05-17 14:26 ` David S. Miller
2002-05-17 14:42 ` Jeff Garzik
2002-05-17 16:24 ` Ivan Kokshaysky
2002-05-17 16:53 ` David S. Miller
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=20020517.051518.35579118.davem@redhat.com \
--to=davem@redhat.com \
--cc=Greg@kroah.com \
--cc=andrew.grover@intel.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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