From: Arnd Bergmann <arnd@arndb.de>
To: Duc Dang <dhdang@apm.com>
Cc: linux-arm <linux-arm-kernel@lists.infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Will Deacon <will.deacon@arm.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
patches <patches@apm.com>,
linux-kernel@vger.kernel.org, Tanmay Inamdar <tinamdar@apm.com>
Subject: Re: [PATCH 1/1] pci: xgene: Enable huge outbound bar support
Date: Fri, 26 Jun 2015 22:43:32 +0200 [thread overview]
Message-ID: <1674778.6xGik39Z0J@wuerfel> (raw)
In-Reply-To: <46305464.n5SOjGAhJb@wuerfel>
On Friday 26 June 2015 22:35:08 Arnd Bergmann wrote:
> > >
> > > Can you configure one of the two windows as prefetchable for improved performance?
> > >
> > The new huge window will be prefetchable.
>
> The DT marks it as non-prefetchable, so the kernel will now try to allocate
> space for non-prefetchable BARs from this area, which is a bug. If the second
> memory window is always prefetchable, you have to mark it accordingly in DT,
> to prevent it from being used for normal 64 bit BARs.
Forget what I wrote here, I just remembered that 64-bit BARs are by definition
prefetchable. You should still mark the range accordingly in DT for correct
operation, but it won't be used for non-prefetchable 64-bit BARs if you don't
because they do not exist.
Arnd
next prev parent reply other threads:[~2015-06-26 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 1:05 [PATCH 1/1] pci: xgene: Enable huge outbound bar support Duc Dang
2015-06-26 7:59 ` Arnd Bergmann
2015-06-26 18:56 ` Duc Dang
[not found] ` <CADaLNDkck5TaG48sjF9y1wrXTzUeVkYOsXw7Dm8a629KqBafFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-26 20:35 ` Arnd Bergmann
2015-06-26 20:43 ` Arnd Bergmann [this message]
2015-06-26 21:56 ` Duc Dang
2015-06-30 18:22 ` [PATCH v2 0/2] pci: xgene: Add multiple memory ranges support Duc Dang
2015-06-30 18:22 ` [PATCH v2 1/2] arm64: dts: Add 1 more window with large size for X-Gene PCIe nodes Duc Dang
2015-06-30 18:22 ` [PATCH v2 2/2] pci: xgene: Fix driver to handle multiple memory ranges Duc Dang
2015-07-06 23:28 ` [PATCH v2 0/2] pci: xgene: Add multiple memory ranges support Duc Dang
2015-07-09 11:47 ` Arnd Bergmann
2015-07-09 21:20 ` [PATCH v3 " Duc Dang
2015-07-09 21:20 ` [PATCH v3 1/2] arm64: dts: Add 1 more window with large size for X-Gene PCIe nodes Duc Dang
2015-07-09 21:20 ` [PATCH v3 2/2] pci: xgene: Fix driver to handle multiple memory ranges Duc Dang
2015-07-21 16:14 ` [PATCH v3 0/2] pci: xgene: Add multiple memory ranges support Bjorn Helgaas
2015-07-21 18:11 ` Duc Dang
2015-07-09 21:24 ` [PATCH v2 " Duc Dang
2015-06-26 14:26 ` [PATCH 1/1] pci: xgene: Enable huge outbound bar support Bjorn Helgaas
2015-06-26 17:26 ` Duc Dang
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=1674778.6xGik39Z0J@wuerfel \
--to=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dhdang@apm.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@apm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tinamdar@apm.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox