From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Alistair Popple <alistair@popple.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Russell Currey <ruscur@russell.cc>
Subject: [PATCH kernel 0/2] powerpc/powernv: Rework sketchy bypass
Date: Fri, 1 Jun 2018 18:10:26 +1000 [thread overview]
Message-ID: <20180601081028.29401-1-aik@ozlabs.ru> (raw)
I came across this adhoc implementation and thought it could use some
polishing. This fixes memory leaks and add P9 support. Based on the current
upstream.
Please comment. Thanks.
Alexey Kardashevskiy (2):
powerpc/powernv: Reuse existing TCE code for sketchy bypass
powerpc/powernv: Define PHB4 type and enable sketchy bypass on POWER9
arch/powerpc/platforms/powernv/pci.h | 1 +
arch/powerpc/platforms/powernv/pci-ioda.c | 76 +++++++++++++++++--------------
2 files changed, 44 insertions(+), 33 deletions(-)
--
2.11.0
next reply other threads:[~2018-06-01 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 8:10 Alexey Kardashevskiy [this message]
2018-06-01 8:10 ` [PATCH kernel 1/2] powerpc/powernv: Reuse existing TCE code for sketchy bypass Alexey Kardashevskiy
2018-06-16 1:04 ` Benjamin Herrenschmidt
2018-07-02 8:50 ` Alexey Kardashevskiy
2018-06-01 8:10 ` [PATCH kernel 2/2] powerpc/powernv: Define PHB4 type and enable sketchy bypass on POWER9 Alexey Kardashevskiy
2018-06-16 1:05 ` Benjamin Herrenschmidt
2018-06-18 2:13 ` Alexey Kardashevskiy
2018-06-18 4:44 ` Benjamin Herrenschmidt
2018-06-18 7:20 ` Alexey Kardashevskiy
2018-06-15 9:01 ` [PATCH kernel 0/2] powerpc/powernv: Rework sketchy bypass Alexey Kardashevskiy
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=20180601081028.29401-1-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ruscur@russell.cc \
/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).