From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: Sethi Varun-B16395 <B16395@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: pci overmapping
Date: Thu, 2 May 2013 12:13:59 -0500 [thread overview]
Message-ID: <1367514839.24411.12@snotra> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E15035C8E18@039-SN1MPN1-002.039d.mgd.msft.net> (from B08248@freescale.com on Thu May 2 12:05:42 2013)
On 05/02/2013 12:05:42 PM, Yoder Stuart-B08248 wrote:
> Kumar,
>=20
> In fsl_pci.c there is a change you made a while back:
> "powerpc/fsl: Setup PCI inbound window based on actual amount of =20
> memory"
>=20
> ...and there is this comment in the code:
>=20
> /* PCIe can overmap inbound & outbound since RX & TX are =20
> separated */
> if (early_find_capability(hose, 0, 0, PCI_CAP_ID_EXP)) {
>=20
> You are implying that PCIe can overmap and PCI can't. Why is
> that? (I'm assuming that 'overmap' means that inbound window
> can extend beyond the end of ram.)
Shouldn't the concern be whether we're overlapping outbound, not merely =20
whether we go beyond the end of RAM?
And couldn't inbound/outbound overlap be an issue even on PCIe, if =20
there's a PCI bridge underneath it?
-Scott=
next prev parent reply other threads:[~2013-05-02 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 17:05 pci overmapping Yoder Stuart-B08248
2013-05-02 17:13 ` Scott Wood [this message]
2013-05-02 18:09 ` Sethi Varun-B16395
2013-05-02 18:19 ` Scott Wood
2013-05-03 5:29 ` Sethi Varun-B16395
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=1367514839.24411.12@snotra \
--to=scottwood@freescale.com \
--cc=B08248@freescale.com \
--cc=B16395@freescale.com \
--cc=linuxppc-dev@lists.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 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.