linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
	"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: Fri, 17 May 2002 14:47:55 +0400	[thread overview]
Message-ID: <20020517144755.A16767@jurassic.park.msu.ru> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7E45@orsmsx111.jf.intel.com> <3CE4098E.2070808@mandrakesoft.com>

On Thu, May 16, 2002 at 03:33:34PM -0400, Jeff Garzik wrote:
> 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.

We already have it - void *sysdata. Host-to-PCI (domain) controllers might
be totally different even inside any given architecture, so trying to
make this more generic would be pointless - you will end up with a pointer
to arch/device specific data anyway.
I can think of the only case where domain info might be interesting - if
some device wants to know whether it can talk to another device directly.
We have pci_controller_num(pdev) for this.

Ivan.

  parent reply	other threads:[~2002-05-17 10:48 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 [this message]
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=20020517144755.A16767@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=Greg@kroah.com \
    --cc=andrew.grover@intel.com \
    --cc=davem@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).