From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "Patrick Mochel (mochel@osdl.org)" <mochel@osdl.org>,
"'davem@redhat.com'" <davem@redhat.com>,
"'Greg@kroah.com'" <Greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: pci segments/domains
Date: Thu, 16 May 2002 15:33:34 -0400 [thread overview]
Message-ID: <3CE4098E.2070808@mandrakesoft.com> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7E45@orsmsx111.jf.intel.com>
Grover, Andrew wrote:
>Well, ACPI calls them "segments" but a previous discussion (c.f. "RFC:
>Changes for PCI" from a year ago) called them domains.
>
>I don't care what they're called, but I wanted to bring them up and see what
>everyone thought about how best to implement them, or at least if anyone had
>an objection to adding a "segment" parameter to pci_scan_root.
>
>I certainly don't have a machine that uses these but some people do, and it
>sounds like it would be nice to handle them in an arch-neutral way.
>
alpha and sparc64 at least already do them.
I wouldn't mind making the PCI domain support a bit more explicit,
though. I think it's fair to be able to obtain a pointer to "struct
pci_domain", which would most likely be defined in asm/pci.h for each arch.
Jeff
next prev parent reply other threads:[~2002-05-16 19:35 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 [this message]
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
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=3CE4098E.2070808@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Greg@kroah.com \
--cc=andrew.grover@intel.com \
--cc=davem@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.