From: "Isaac J. Manjarres" <isaacm@codeaurora.org>
To: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Isaac J. Manjarres" <isaacm@codeaurora.org>,
kernel-team@android.com, pdaly@codeaurora.org, will@kernel.org,
robin.murphy@arm.com, pratikp@codeaurora.org
Subject: [RFC PATCH 0/3] iommu: Permit modular builds of io-pgtable drivers
Date: Fri, 18 Dec 2020 00:38:39 -0800 [thread overview]
Message-ID: <1608280722-19841-1-git-send-email-isaacm@codeaurora.org> (raw)
The goal of the Generic Kernel Image (GKI) effort is to have a common
image that works across multiple Android devices. This involves generating
a kernel image that has core features integrated into it, while SoC specific
functionality can be added to the kernel for the device as a module.
Along with modularizing IOMMU drivers, this also means building the io-pgtable
code as modules, which allows for SoC vendors to only include the io-pgtable
implementations that they use. For example, GKI for arm64 must include
support for both the IOMMU ARM LPAE/V7S formats at the moment. Having the code
for both formats as modules allows SoC vendors to only provide the page table
format that they use, along with their IOMMU driver.
Modularizing both io-pgtable.c, as well as the io-pgtable-arm[-v7s].c files,
works out rather nicely, as the main interface that clients use to interact
with the page tables is already exported (i.e. alloc_io_pgtable_ops and
free_io_pgtable_ops). It also makes it so that neither the io-pgtable-arm[-v7s]
modules or the io-pgtable modules can be unloaded without unloading the IOMMU
driver, which can only happen when there aren't any references to the IOMMU
driver module.
Thanks in advance for the feedback,
Isaac J. Manjarres
Isaac J. Manjarres (3):
iommu/io-pgtable-arm: Prepare for modularization
iommu/io-pgtable: Prepare for modularization
iommu/io-pgtable: Allow building as a module
drivers/iommu/Kconfig | 6 +++---
drivers/iommu/io-pgtable-arm-v7s.c | 4 ++++
drivers/iommu/io-pgtable-arm.c | 8 ++++++++
drivers/iommu/io-pgtable.c | 7 +++++--
4 files changed, 20 insertions(+), 5 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: "Isaac J. Manjarres" <isaacm@codeaurora.org>
To: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Isaac J. Manjarres" <isaacm@codeaurora.org>,
will@kernel.org, joro@8bytes.org, robin.murphy@arm.com,
pdaly@codeaurora.org, pratikp@codeaurora.org,
kernel-team@android.com
Subject: [RFC PATCH 0/3] iommu: Permit modular builds of io-pgtable drivers
Date: Fri, 18 Dec 2020 00:38:39 -0800 [thread overview]
Message-ID: <1608280722-19841-1-git-send-email-isaacm@codeaurora.org> (raw)
The goal of the Generic Kernel Image (GKI) effort is to have a common
image that works across multiple Android devices. This involves generating
a kernel image that has core features integrated into it, while SoC specific
functionality can be added to the kernel for the device as a module.
Along with modularizing IOMMU drivers, this also means building the io-pgtable
code as modules, which allows for SoC vendors to only include the io-pgtable
implementations that they use. For example, GKI for arm64 must include
support for both the IOMMU ARM LPAE/V7S formats at the moment. Having the code
for both formats as modules allows SoC vendors to only provide the page table
format that they use, along with their IOMMU driver.
Modularizing both io-pgtable.c, as well as the io-pgtable-arm[-v7s].c files,
works out rather nicely, as the main interface that clients use to interact
with the page tables is already exported (i.e. alloc_io_pgtable_ops and
free_io_pgtable_ops). It also makes it so that neither the io-pgtable-arm[-v7s]
modules or the io-pgtable modules can be unloaded without unloading the IOMMU
driver, which can only happen when there aren't any references to the IOMMU
driver module.
Thanks in advance for the feedback,
Isaac J. Manjarres
Isaac J. Manjarres (3):
iommu/io-pgtable-arm: Prepare for modularization
iommu/io-pgtable: Prepare for modularization
iommu/io-pgtable: Allow building as a module
drivers/iommu/Kconfig | 6 +++---
drivers/iommu/io-pgtable-arm-v7s.c | 4 ++++
drivers/iommu/io-pgtable-arm.c | 8 ++++++++
drivers/iommu/io-pgtable.c | 7 +++++--
4 files changed, 20 insertions(+), 5 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2020-12-18 8:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 8:38 Isaac J. Manjarres [this message]
2020-12-18 8:38 ` [RFC PATCH 0/3] iommu: Permit modular builds of io-pgtable drivers Isaac J. Manjarres
2020-12-18 8:38 ` [PATCH 1/3] iommu/io-pgtable-arm: Prepare for modularization Isaac J. Manjarres
2020-12-18 8:38 ` Isaac J. Manjarres
2020-12-18 12:38 ` Robin Murphy
2020-12-18 12:38 ` Robin Murphy
2020-12-18 12:38 ` Robin Murphy
2020-12-18 18:59 ` isaacm
2020-12-18 18:59 ` isaacm
2020-12-21 15:22 ` Robin Murphy
2020-12-21 15:22 ` Robin Murphy
2020-12-21 15:22 ` Robin Murphy
2020-12-22 0:54 ` isaacm
2020-12-22 0:54 ` isaacm
2020-12-18 8:38 ` [PATCH 2/3] iommu/io-pgtable: " Isaac J. Manjarres
2020-12-18 8:38 ` Isaac J. Manjarres
2020-12-18 8:38 ` [PATCH 3/3] iommu/io-pgtable: Allow building as a module Isaac J. Manjarres
2020-12-18 8:38 ` Isaac J. Manjarres
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=1608280722-19841-1-git-send-email-isaacm@codeaurora.org \
--to=isaacm@codeaurora.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pdaly@codeaurora.org \
--cc=pratikp@codeaurora.org \
--cc=robin.murphy@arm.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.