From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: yan@linux.vnet.ibm.com, Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH v3 0/6] Support M64 Window
Date: Mon, 21 Jul 2014 14:42:29 +1000 [thread overview]
Message-ID: <1405917755-28830-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
This version is rebased on top of Gavin's patches of EEH support for guest and
related fixes which are supposed to be merged in 3.17.
Currently, all MMIO resources, including 64-bits MMIO resources are hooked
to PHB 32-bits MMIO BAR, which has limited space. If there're PCI devices
with large 64-bits MMIO BAR (could reach 1GB), we're running out of MMIO
resources (as well as PE numbers) quickly. The patchset reuses the M32
infrastructure to support M64:
* The last M64 BAR covers all M64 aperatus and that's shared by all PEs.
* Reuse ppc_md.pcibios_window_alignment() to affect resource assignment
in PCI core so that we can get well segmented 64-bits window of PCI
bridges.
* One PCI bus might require multiple discrete M64 segment. We invent
if we're going to unfreeze any one in the group.
Changelog
=========
v2 -> v3:
* Use separate OPAL API to freeze PE.
v1 -> v2:
* Avoid overwritting PE flags.
* Don't return segment alignment if M64 is not supported.
* Output M64 total size and segment size together with M32 and IO
Gavin Shan (5):
powerpc/powernv: Allow to freeze PE
powerpc/powernv: Split ioda_eeh_get_state()
powerpc/powernv: Handle compound PE
powerpc/powernv: Handle compound PE for EEH
powerpc/powernv: Handle compound PE in config accessors
Guo Chao (1):
powerpc/powernv: Enable M64 aperatus for PHB3
arch/powerpc/include/asm/opal.h | 17 +-
arch/powerpc/platforms/powernv/eeh-ioda.c | 291 +++++++++-------
arch/powerpc/platforms/powernv/opal-wrappers.S | 1 +
arch/powerpc/platforms/powernv/pci-ioda.c | 444 +++++++++++++++++++++++--
arch/powerpc/platforms/powernv/pci.c | 87 +++--
arch/powerpc/platforms/powernv/pci.h | 23 ++
6 files changed, 694 insertions(+), 169 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-07-21 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 4:42 Gavin Shan [this message]
2014-07-21 4:42 ` [PATCH v3 1/6] powerpc/powernv: Enable M64 aperatus for PHB3 Gavin Shan
2014-07-21 4:42 ` [PATCH v3 2/6] powerpc/powernv: Allow to freeze PE Gavin Shan
2014-07-21 4:42 ` [PATCH v3 3/6] powerpc/powernv: Split ioda_eeh_get_state() Gavin Shan
2014-07-21 4:42 ` [PATCH v3 4/6] powerpc/powernv: Handle compound PE Gavin Shan
2014-07-21 4:42 ` [PATCH v3 5/6] powerpc/powernv: Handle compound PE for EEH Gavin Shan
2014-07-21 4:42 ` [PATCH v3 6/6] powerpc/powernv: Handle compound PE in config accessors Gavin Shan
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=1405917755-28830-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yan@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).