From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Sam Bobroff <sbobroff@linux.ibm.com>,
kvm-ppc@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH kernel 0/2] powerpc/iommu: Redo iommu groups
Date: Thu, 18 Oct 2018 18:52:41 +1100 [thread overview]
Message-ID: <20181018075243.4798-1-aik@ozlabs.ru> (raw)
The aim is to:
1. simplify the code
2. get rid of iommu_table_group_link.
Now: iommu_table points to a list of iommu_table_group_link which
point to iommu_table_group (powerpc specific part of an IOMMU group);
one iommu_table_group_link per iommu_table_group per IODA PE.
Plan: add support of multiple IODA PEs per one generic IOMMU group,
I am just not sure how yet. We already have a case of GPU+NPU groups,
and a worse one is coming, with 3xGPU + 6xNVLink2.
Please comment. Thanks.
Alexey Kardashevskiy (2):
powerpc/pseries: Remove IOMMU API support for non-LPAR systems
powerpc/powernv/pseries: Rework device adding to IOMMU groups
arch/powerpc/include/asm/iommu.h | 12 +++----
arch/powerpc/kernel/iommu.c | 58 ++-----------------------------
arch/powerpc/platforms/powernv/pci-ioda.c | 10 +-----
arch/powerpc/platforms/powernv/pci.c | 43 ++++++++++++++++++++++-
arch/powerpc/platforms/pseries/iommu.c | 55 ++++++++++++++---------------
5 files changed, 76 insertions(+), 102 deletions(-)
--
2.11.0
next reply other threads:[~2018-10-18 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 7:52 Alexey Kardashevskiy [this message]
2018-10-18 7:52 ` [PATCH kernel 1/2] powerpc/pseries: Remove IOMMU API support for non-LPAR systems Alexey Kardashevskiy
2018-11-08 5:11 ` David Gibson
2018-10-18 7:52 ` [PATCH kernel 2/2] powerpc/powernv/pseries: Rework device adding to IOMMU groups Alexey Kardashevskiy
2018-11-08 5:18 ` David Gibson
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=20181018075243.4798-1-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sbobroff@linux.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).