From: Ira Snyder <iws@ovro.caltech.edu>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-pci@vger.kernel.org,
Benjamin Herrenschmidt <benh@au1.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: tracking of PCI address space
Date: Wed, 8 Apr 2009 14:49:32 -0700 [thread overview]
Message-ID: <20090408214932.GA31970@ovro.caltech.edu> (raw)
In-Reply-To: <E942C580-7C39-44AB-B207-C65CDE0B5292@kernel.crashing.org>
On Wed, Apr 08, 2009 at 03:53:55PM -0500, Kumar Gala wrote:
> I was wondering if we have anything that tracks regions associated with
> the "inbound" side of a pci_bus.
>
> What I mean is on embedded PPC we have window/mapping registers for both
> inbound (accessing memory on the SoC) and outbound (access PCI device
> MMIO, IO etc). The combination of the inbound & outbound convey what
> exists in the PCI address space vs CPU physical address space (and how to
> map from one to the other). Today in the PPC land we only attach
> outbound windows to the pci_bus. So technically the inbound side
> information (like what subset of physical memory is visible on the PCI
> bus) seems to be lost.
>
To the best of my knowledge there is no API to set inbound windows in
Linux. I've been implementing a virtio-over-PCI driver which needs the
inbound windows. I set them up myself during driver probe, using
get_immrbase() to get the IMMR registers. This board is a PCI Slave /
Agent, it doesn't even have PCI support compiled into the kernel.
Ira
next prev parent reply other threads:[~2009-04-08 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 20:53 tracking of PCI address space Kumar Gala
2009-04-08 21:49 ` Ira Snyder [this message]
2009-04-08 21:53 ` Kumar Gala
2009-04-09 6:21 ` Benjamin Herrenschmidt
2009-04-09 6:44 ` Tirumala Reddy Marri
2009-04-09 6:55 ` Grant Grundler
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=20090408214932.GA31970@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=benh@au1.ibm.com \
--cc=galak@kernel.crashing.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).