From: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
To: <iommu@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>
Cc: <joro@8bytes.org>, <jgg@nvidia.com>, <kevin.tian@intel.com>,
<nicolinc@nvidia.com>, <mshavit@google.com>,
<robin.murphy@arm.com>, <will@kernel.org>,
<joao.m.martins@oracle.com>, <jiangkunkun@huawei.com>,
<zhukeqian1@huawei.com>, <linuxarm@huawei.com>
Subject: [PATCH v2 0/4] iommu/smmuv3: Add IOMMUFD dirty tracking support for SMMUv3
Date: Thu, 22 Feb 2024 09:49:19 +0000 [thread overview]
Message-ID: <20240222094923.33104-1-shameerali.kolothum.thodi@huawei.com> (raw)
Hi,
This is revisiting the earlier attempts [1, 2] to use SMMUv3 HTTU feature
for dirty page tracking. The Intel/AMD support is already mainline.
The code is now based on the new IOMMUFD APIs and is rebased on
Jason's SMMUv3 driver refactor series[3].
Basic sanity tests are done using an emulation setup and on a test
hardware setup. Block page split/merge(BBML) is not part of this
series. I am planning to send it separately.
v1 --> v2:
https://lore.kernel.org/linux-iommu/20231128094940.1344-1-shameerali.kolothum.thodi@huawei.com/
Addressed review comments from Jason and Joao(Thanks)
-Moved dirty_ops setting to domain finalise(patch #3)
-Only enable DBM for stage 1 if domain_alloc_user() requests it.
-Changed IO page table walker(patch #2) and tested with 4KB/16KB/64KB
with l1/l2/l3 traversal.(The earlier one had a bug where it fails to
walk L3 level).
-Rearranged patches a bit to improve bi-sectability.
-Rebased on top of Jason's v5 of SMMUv3 new API series git.
Please take a look and let me know your feedback.
Thanks,
Shameer
1. https://lore.kernel.org/lkml/20210413085457.25400-1-zhukeqian1@huawei.com/
2. https://lore.kernel.org/linux-iommu/20230518204650.14541-1-joao.m.martins@oracle.com/
3. https://github.com/jgunthorpe/linux/commits/smmuv3_newapi
Jean-Philippe Brucker (1):
iommu/arm-smmu-v3: Add feature detection for HTTU
Joao Martins (1):
iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc
Kunkun Jiang (1):
iommu/arm-smmu-v3: Enable HTTU for stage1 with io-pgtable mapping
Shameer Kolothum (1):
iommu/io-pgtable-arm: Add read_and_clear_dirty() support
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 142 +++++++++++++++++---
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 8 ++
drivers/iommu/io-pgtable-arm.c | 133 +++++++++++++++++-
include/linux/io-pgtable.h | 4 +
4 files changed, 263 insertions(+), 24 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-22 9:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:49 Shameer Kolothum [this message]
2024-02-22 9:49 ` [PATCH v2 1/4] iommu/arm-smmu-v3: Add feature detection for HTTU Shameer Kolothum
2024-04-23 14:41 ` Ryan Roberts
2024-04-23 14:52 ` Jason Gunthorpe
2024-04-24 10:04 ` Ryan Roberts
2024-04-24 12:23 ` Jason Gunthorpe
2024-04-24 12:59 ` Ryan Roberts
2024-04-24 13:20 ` Shameerali Kolothum Thodi
2024-04-24 13:32 ` Jason Gunthorpe
2024-04-24 13:43 ` Shameerali Kolothum Thodi
2024-04-24 14:21 ` Jason Gunthorpe
2024-04-24 8:01 ` Shameerali Kolothum Thodi
2024-04-24 8:28 ` Ryan Roberts
2024-02-22 9:49 ` [PATCH v2 2/4] iommu/io-pgtable-arm: Add read_and_clear_dirty() support Shameer Kolothum
2024-04-23 15:56 ` Ryan Roberts
2024-04-24 8:01 ` Shameerali Kolothum Thodi
2024-04-24 8:36 ` Ryan Roberts
2024-02-22 9:49 ` [PATCH v2 3/4] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc Shameer Kolothum
2024-02-22 11:04 ` Joao Martins
2024-02-22 11:31 ` Shameerali Kolothum Thodi
2024-02-22 11:37 ` Joao Martins
2024-02-22 12:24 ` Shameerali Kolothum Thodi
2024-02-22 13:11 ` Jason Gunthorpe
2024-02-22 13:23 ` Joao Martins
2024-03-08 14:31 ` Jason Gunthorpe
2024-04-23 16:27 ` Ryan Roberts
2024-04-23 16:39 ` Jason Gunthorpe
2024-04-23 16:50 ` Ryan Roberts
2024-04-24 8:27 ` Shameerali Kolothum Thodi
2024-02-22 9:49 ` [PATCH v2 4/4] iommu/arm-smmu-v3: Enable HTTU for stage1 with io-pgtable mapping Shameer Kolothum
2024-03-08 14:32 ` Jason Gunthorpe
2024-04-23 16:45 ` Ryan Roberts
2024-04-23 17:32 ` Jason Gunthorpe
2024-04-24 7:58 ` Ryan Roberts
2024-04-24 12:15 ` Jason Gunthorpe
2024-04-24 12:45 ` Ryan Roberts
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=20240222094923.33104-1-shameerali.kolothum.thodi@huawei.com \
--to=shameerali.kolothum.thodi@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jiangkunkun@huawei.com \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=zhukeqian1@huawei.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 read-only IMAP folder(s) and NNTP newsgroup(s).