From: Guo Chao <yan@linux.vnet.ibm.com>
To: linux-pci@vger.kernel.org
Cc: bhelgaas@google.com, yinghai@kernel.org
Subject: [RFC PATCH 0/3] Make 64-bit prefetchable MMIO work
Date: Tue, 19 Nov 2013 14:36:55 +0800 [thread overview]
Message-ID: <1384843018-9479-1-git-send-email-yan@linux.vnet.ibm.com> (raw)
Resource assignment code does not work properly after we expose 64-bit
prefetchable MMIO window in PowerNV platform.
# ROM BAR get 4G-above address.
This is because default value of PCIBIOS_MAX_MEM_32 is -1
which makes it useless in 64-bit platform. After
fixing this ...
# ROM BAR can't get any address.
This is because PCIBIOS_MAX_MEM_32 is actually a PCI address
but functions as a CPU address. After fixing this ...
# 64-bit prefetchable address is never used.
This is because root bridge's IORESOURCE_MEM_64 is reset due to
ROM BARs, which makes it not quilify to get 4G-above prefetchable
address from host bridge. The 64-bit 4G-above prefetchable window
is not used at all in the end.
Nothing is really broken currently. This is just a RFC series, preparing
for later PowerNV 64-bit MMIO work.
Guo Chao (3):
PCI: do not compare CPU address with PCI address
PCI: set proper default value of PCIBIOS_MAX_MEM_32
PCI: do not reset bridge's IORESOURCE_MEM_64 flag for ROM BAR
arch/x86/include/asm/pci.h | 1 -
drivers/pci/bus.c | 65 ++++++++++++++++++++++++++++++++++++++++++++--
drivers/pci/setup-bus.c | 3 ++-
include/linux/pci.h | 2 +-
4 files changed, 66 insertions(+), 5 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-11-19 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 6:36 Guo Chao [this message]
2013-11-19 6:36 ` [RFC PATCH 1/3] PCI: do not compare CPU address with PCI address Guo Chao
2013-11-19 19:31 ` Yinghai Lu
2013-11-19 19:35 ` Yinghai Lu
2013-11-19 23:48 ` Bjorn Helgaas
2013-11-19 6:36 ` [RFC PATCH 2/3] PCI: set proper default value of PCIBIOS_MAX_MEM_32 Guo Chao
2013-11-19 6:36 ` [RFC PATCH 3/3] PCI: do not reset bridge's IORESOURCE_MEM_64 flag for ROM BAR Guo Chao
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=1384843018-9479-1-git-send-email-yan@linux.vnet.ibm.com \
--to=yan@linux.vnet.ibm.com \
--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).