From: Jason Gunthorpe <jgg@ziepe.ca>
To: Qinxin Xia <xiaqinxin@huawei.com>
Cc: will@kernel.org, robin.murphy@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
yangyicong@huawei.com, wangzhou1@hisilicon.com,
prime.zeng@hisilicon.com, xuwei5@huawei.com,
fanghao11@huawei.com, jonathan.cameron@huawei.com,
linuxarm@huawei.com
Subject: Re: [PATCH 0/2] iommu: Add io_ptdump debug interface for iommu
Date: Tue, 2 Sep 2025 13:10:28 -0300 [thread overview]
Message-ID: <20250902161028.GC184112@ziepe.ca> (raw)
In-Reply-To: <20250814093005.2040511-1-xiaqinxin@huawei.com>
On Thu, Aug 14, 2025 at 05:30:03PM +0800, Qinxin Xia wrote:
> This patch supports the iopgtable_dump function (similar to kernel_page_dump).
> The IOMMU page table dump debugging function is added to the framework layer.
> Different architectures only need to provide the implemented dump ops.
> It also provides the implementation of ARM SMMUv3 and io-pgtable-arm.
>
> Qinxin Xia (2):
> iommu/debug: Add IOMMU page table dump debug facility
> iommu/io-pgtable: Add ARM SMMUv3 page table dump support
I'd prefer we do this on top of iommu pt please, I don't want to
further deeping the hole of changing all the page table code in all
drivers for debugfs.
Jason
next prev parent reply other threads:[~2025-09-02 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 9:30 [PATCH 0/2] iommu: Add io_ptdump debug interface for iommu Qinxin Xia
2025-08-14 9:30 ` [PATCH 1/2] iommu/debug: Add IOMMU page table dump debug facility Qinxin Xia
2025-08-15 6:47 ` kernel test robot
2025-08-15 9:57 ` kernel test robot
2025-09-09 13:06 ` Will Deacon
2025-09-10 2:58 ` Qinxin Xia
2025-09-11 14:58 ` Will Deacon
2025-08-14 9:30 ` [PATCH 2/2] iommu/io-pgtable: Add ARM SMMUv3 page table dump support Qinxin Xia
2025-08-15 9:14 ` kernel test robot
2025-09-02 16:10 ` Jason Gunthorpe [this message]
2025-09-10 3:20 ` [PATCH 0/2] iommu: Add io_ptdump debug interface for iommu Qinxin Xia
2025-09-10 14:15 ` Jason Gunthorpe
2025-09-11 14:08 ` Qinxin Xia
2025-09-15 16:28 ` Jason Gunthorpe
2025-10-18 10:39 ` Qinxin Xia
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=20250902161028.GC184112@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=fanghao11@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=robin.murphy@arm.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=xiaqinxin@huawei.com \
--cc=xuwei5@huawei.com \
--cc=yangyicong@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 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.