From: Bjorn Helgaas <helgaas@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Doug Anderson <dianders@chromium.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>,
linux-pci@vger.kernel.org,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [BUG] rk3399-rockpro64 pcie synchronous external abort
Date: Mon, 11 Nov 2019 18:03:34 -0600 [thread overview]
Message-ID: <20191112000334.GA69183@google.com> (raw)
In-Reply-To: <CAMdYzYo6mKSMXoDR7St1ynUJ9f3sh=0rgNAbbVvFAfJn82VvVQ@mail.gmail.com>
On Sun, Nov 10, 2019 at 10:43:48AM -0500, Peter Geis wrote:
> I plugged in an i350 two port nic and examined the assigned address spaces.
> I've attached it below.
> Judging by the usage, I think this controller has enough address space
> for another two port NIC, and that's about it.
> I'm pretty sure now that the rk3399 controller just doesn't have the
> address space to map larger devices.
> I'm pretty sure the IOMMU would allow us to address system memory as
> pcie address space and overcome this limitation, but I don't know how
> to do that.
I don't think you're out of MMIO space, at least in this instance. It
looks like you have 32MB available and the two-port NIC on bus 01 only
takes 5MB.
The IOMMU is used for DMA (e.g., reads/writes initiated by the NIC),
while the MMIO space is used for CPU programmed I/O (reads/writes done
by the driver running on the CPU).
> The address space for the nic is below:
> f8000000-f8ffffff : axi-base
> fa000000-fbdfffff : MEM
32MB.
> fa000000-fa4fffff : PCI Bus 0000:01
5MB.
> fa000000-fa07ffff : 0000:01:00.0
> fa000000-fa07ffff : igb
> fa080000-fa0fffff : 0000:01:00.0
> fa100000-fa17ffff : 0000:01:00.1
> fa100000-fa17ffff : igb
> fa180000-fa1fffff : 0000:01:00.1
> fa200000-fa27ffff : 0000:01:00.0
> fa280000-fa2fffff : 0000:01:00.0
> fa300000-fa37ffff : 0000:01:00.1
> fa380000-fa3fffff : 0000:01:00.1
> fa400000-fa403fff : 0000:01:00.0
> fa400000-fa403fff : igb
> fa404000-fa407fff : 0000:01:00.1
> fa404000-fa407fff : igb
> fd000000-fdffffff : f8000000.pcie
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Peter Geis <pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Shawn Lin <shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Subject: Re: [BUG] rk3399-rockpro64 pcie synchronous external abort
Date: Mon, 11 Nov 2019 18:03:34 -0600 [thread overview]
Message-ID: <20191112000334.GA69183@google.com> (raw)
In-Reply-To: <CAMdYzYo6mKSMXoDR7St1ynUJ9f3sh=0rgNAbbVvFAfJn82VvVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sun, Nov 10, 2019 at 10:43:48AM -0500, Peter Geis wrote:
> I plugged in an i350 two port nic and examined the assigned address spaces.
> I've attached it below.
> Judging by the usage, I think this controller has enough address space
> for another two port NIC, and that's about it.
> I'm pretty sure now that the rk3399 controller just doesn't have the
> address space to map larger devices.
> I'm pretty sure the IOMMU would allow us to address system memory as
> pcie address space and overcome this limitation, but I don't know how
> to do that.
I don't think you're out of MMIO space, at least in this instance. It
looks like you have 32MB available and the two-port NIC on bus 01 only
takes 5MB.
The IOMMU is used for DMA (e.g., reads/writes initiated by the NIC),
while the MMIO space is used for CPU programmed I/O (reads/writes done
by the driver running on the CPU).
> The address space for the nic is below:
> f8000000-f8ffffff : axi-base
> fa000000-fbdfffff : MEM
32MB.
> fa000000-fa4fffff : PCI Bus 0000:01
5MB.
> fa000000-fa07ffff : 0000:01:00.0
> fa000000-fa07ffff : igb
> fa080000-fa0fffff : 0000:01:00.0
> fa100000-fa17ffff : 0000:01:00.1
> fa100000-fa17ffff : igb
> fa180000-fa1fffff : 0000:01:00.1
> fa200000-fa27ffff : 0000:01:00.0
> fa280000-fa2fffff : 0000:01:00.0
> fa300000-fa37ffff : 0000:01:00.1
> fa380000-fa3fffff : 0000:01:00.1
> fa400000-fa403fff : 0000:01:00.0
> fa400000-fa403fff : igb
> fa404000-fa407fff : 0000:01:00.1
> fa404000-fa407fff : igb
> fd000000-fdffffff : f8000000.pcie
next prev parent reply other threads:[~2019-11-12 0:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 18:55 [BUG] rk3399-rockpro64 pcie synchronous external abort Peter Geis
2019-11-04 18:55 ` Peter Geis
2019-11-09 1:08 ` Peter Geis
2019-11-09 1:08 ` Peter Geis
2019-11-09 16:37 ` Doug Anderson
2019-11-09 16:37 ` Doug Anderson
2019-11-10 15:43 ` Peter Geis
2019-11-10 15:43 ` Peter Geis
2019-11-12 0:03 ` Bjorn Helgaas [this message]
2019-11-12 0:03 ` Bjorn Helgaas
2019-11-12 0:21 ` Peter Geis
2019-11-12 0:21 ` Peter Geis
2019-11-12 0:13 ` Bjorn Helgaas
2019-11-12 0:13 ` Bjorn Helgaas
2019-11-12 0:30 ` Peter Geis
2019-11-12 0:30 ` Peter Geis
2019-11-12 2:29 ` Bjorn Helgaas
2019-11-12 2:29 ` Bjorn Helgaas
2019-11-12 15:55 ` Peter Geis
2019-11-12 15:55 ` Peter Geis
2019-11-12 19:15 ` Robin Murphy
2019-11-12 19:15 ` Robin Murphy
2019-11-12 19:41 ` Peter Geis
2019-11-12 19:41 ` Peter Geis
2019-11-13 1:06 ` Peter Geis
2019-11-13 1:06 ` Peter Geis
2019-11-13 1:19 ` Peter Geis
2019-11-13 1:19 ` Peter Geis
2019-11-21 0:36 ` Peter Geis
2019-11-21 0:36 ` Peter Geis
2019-11-21 2:03 ` Shawn Lin
2019-11-21 2:03 ` Shawn Lin
2019-11-22 1:02 ` Peter Geis
2019-11-22 1:02 ` Peter Geis
2019-11-22 14:11 ` Peter Geis
2019-11-22 14:11 ` Peter Geis
2019-11-22 14:36 ` Bjorn Helgaas
2019-11-22 14:36 ` Bjorn Helgaas
2019-11-22 15:08 ` Peter Geis
2019-11-22 15:08 ` Peter Geis
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=20191112000334.GA69183@google.com \
--to=helgaas@kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=shawn.lin@rock-chips.com \
/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.