From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Subject: Re: PCI resource allocation not using pref 64-bit
Date: Thu, 23 Jun 2016 01:42:48 +1000 [thread overview]
Message-ID: <1466610168.11733.7.camel@kernel.crashing.org> (raw)
In-Reply-To: <1466579045.4089.22.camel@kernel.crashing.org>
On Wed, 2016-06-22 at 17:04 +1000, Benjamin Herrenschmidt wrote:
> Hi folks !
>
> So on my POWER9 simulator, I noticed that the PCI code isn't assigning
> any BAR to my 64-bit prefetchable window.
Problem found ... for various reasons the "windows" registers of the
root complex are emulated in firmware and the emulation wasn't properly
masking (and OR'ing 1) in the prefetchable ones, thus Linux was ditching
them.
Sorry for the noise..
Cheers,
Ben.
prev parent reply other threads:[~2016-06-22 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 7:04 PCI resource allocation not using pref 64-bit Benjamin Herrenschmidt
2016-06-22 15:42 ` Benjamin Herrenschmidt [this message]
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=1466610168.11733.7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.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).