linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Mostafa Saleh <smostafa@google.com>
Cc: linux-mm@kvack.org, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	corbet@lwn.net, joro@8bytes.org, will@kernel.org,
	robin.murphy@arm.com, akpm@linux-foundation.org, vbabka@suse.cz,
	surenb@google.com, mhocko@suse.com, jackmanb@google.com,
	hannes@cmpxchg.org, ziy@nvidia.com, david@redhat.com,
	lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	rppt@kernel.org, xiaqinxin@huawei.com, rdunlap@infradead.org
Subject: Re: [PATCH v4 2/4] iommu: Add calls for IOMMU_DEBUG_PAGEALLOC
Date: Mon, 15 Dec 2025 11:30:39 +0800	[thread overview]
Message-ID: <7186caa3-13c0-4629-a07f-162c00138ad9@linux.intel.com> (raw)
In-Reply-To: <aTxiefxT08hbUPsd@google.com>

On 12/13/25 02:44, Mostafa Saleh wrote:
> On Fri, Dec 12, 2025 at 10:33:20AM +0800, Baolu Lu wrote:
>> On 12/11/25 20:59, Mostafa Saleh wrote:
>>> Add calls for the new iommu debug config IOMMU_DEBUG_PAGEALLOC:
>>> - iommu_debug_init: Enable the debug mode if configured by the user.
>>> - iommu_debug_map: Track iommu pages mapped, using physical address.
>>> - iommu_debug_unmap_begin: Track start of iommu unmap operation, with
>>>     IOVA and size.
>>> - iommu_debug_unmap_end: Track the end of unmap operation, passing the
>>>     actual unmapped size versus the tracked one at unmap_begin.
>>>
>>> We have to do the unmap_begin/end as once pages are unmapped we lose
>>> the information of the physical address.
>>> This is racy, but the API is racy by construction as it uses refcounts
>>> and doesn't attempt to lock/synchronize with the IOMMU API as that will
>>> be costly, meaning that possibility of false negative exists.
>>>
>>> Signed-off-by: Mostafa Saleh<smostafa@google.com>
>>> ---
>>>    drivers/iommu/iommu-debug-pagealloc.c | 28 +++++++++++++
>>>    drivers/iommu/iommu-priv.h            | 58 +++++++++++++++++++++++++++
>>>    drivers/iommu/iommu.c                 | 11 ++++-
>>>    include/linux/iommu-debug-pagealloc.h |  1 +
>>>    4 files changed, 96 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/iommu/iommu-debug-pagealloc.c b/drivers/iommu/iommu-debug-pagealloc.c
>>> index 4022e9af7f27..1d343421da98 100644
>>> --- a/drivers/iommu/iommu-debug-pagealloc.c
>>> +++ b/drivers/iommu/iommu-debug-pagealloc.c
>>> @@ -5,11 +5,15 @@
>>>     * IOMMU API debug page alloc sanitizer
>>>     */
>>>    #include <linux/atomic.h>
>>> +#include <linux/iommu.h>
>>>    #include <linux/iommu-debug-pagealloc.h>
>>>    #include <linux/kernel.h>
>>>    #include <linux/page_ext.h>
>>> +#include "iommu-priv.h"
>>> +
>>>    static bool needed;
>>> +DEFINE_STATIC_KEY_FALSE(iommu_debug_initialized);
>>>    struct iommu_debug_metadata {
>>>    	atomic_t ref;
>>> @@ -25,6 +29,30 @@ struct page_ext_operations page_iommu_debug_ops = {
>>>    	.need = need_iommu_debug,
>>>    };
>>> +void __iommu_debug_map(struct iommu_domain *domain, phys_addr_t phys, size_t size)
>>> +{
>>> +}
>>> +
>>> +void __iommu_debug_unmap_begin(struct iommu_domain *domain,
>>> +			       unsigned long iova, size_t size)
>>> +{
>>> +}
>>> +
>>> +void __iommu_debug_unmap_end(struct iommu_domain *domain,
>>> +			     unsigned long iova, size_t size,
>>> +			     size_t unmapped)
>>> +{
>>> +}
>>> +
>>> +void iommu_debug_init(void)
>>> +{
>>> +	if (!needed)
>>> +		return;
>>> +
>>> +	pr_info("iommu: Debugging page allocations, expect overhead or disable iommu.debug_pagealloc");
>>> +	static_branch_enable(&iommu_debug_initialized);
>>> +}
>>> +
>>>    static int __init iommu_debug_pagealloc(char *str)
>>>    {
>>>    	return kstrtobool(str, &needed);
>>> diff --git a/drivers/iommu/iommu-priv.h b/drivers/iommu/iommu-priv.h
>>> index c95394cd03a7..aaffad5854fc 100644
>>> --- a/drivers/iommu/iommu-priv.h
>>> +++ b/drivers/iommu/iommu-priv.h
>>> @@ -5,6 +5,7 @@
>>>    #define __LINUX_IOMMU_PRIV_H
>>>    #include <linux/iommu.h>
>>> +#include <linux/iommu-debug-pagealloc.h>
>>>    #include <linux/msi.h>
>>>    static inline const struct iommu_ops *dev_iommu_ops(struct device *dev)
>>> @@ -65,4 +66,61 @@ static inline int iommufd_sw_msi(struct iommu_domain *domain,
>>>    int iommu_replace_device_pasid(struct iommu_domain *domain,
>>>    			       struct device *dev, ioasid_t pasid,
>>>    			       struct iommu_attach_handle *handle);
>>> +
>>> +#ifdef CONFIG_IOMMU_DEBUG_PAGEALLOC
>>> +
>>> +void __iommu_debug_map(struct iommu_domain *domain, phys_addr_t phys,
>>> +		       size_t size);
>>> +void __iommu_debug_unmap_begin(struct iommu_domain *domain,
>>> +			       unsigned long iova, size_t size);
>>> +void __iommu_debug_unmap_end(struct iommu_domain *domain,
>>> +			     unsigned long iova, size_t size, size_t unmapped);
>>> +
>>> +static inline void iommu_debug_map(struct iommu_domain *domain,
>>> +				   phys_addr_t phys, size_t size)
>>> +{
>>> +	if (static_branch_unlikely(&iommu_debug_initialized))
>>> +		__iommu_debug_map(domain, phys, size);
>>> +}
>>> +
>>> +static inline void iommu_debug_unmap_begin(struct iommu_domain *domain,
>>> +					   unsigned long iova, size_t size)
>>> +{
>>> +	if (static_branch_unlikely(&iommu_debug_initialized))
>>> +		__iommu_debug_unmap_begin(domain, iova, size);
>>> +}
>>> +
>>> +static inline void iommu_debug_unmap_end(struct iommu_domain *domain,
>>> +					 unsigned long iova, size_t size,
>>> +					 size_t unmapped)
>>> +{
>>> +	if (static_branch_unlikely(&iommu_debug_initialized))
>>> +		__iommu_debug_unmap_end(domain, iova, size, unmapped);
>>> +}
>> I am wondering whether it would be better if we move iommu_debug_map()
>> to iommu-debug-pagealloc.c,
>>
>> void iommu_debug_map(struct iommu_domain *domain,
>> 		     phys_addr_t phys, size_t size)
>> {
>> 	if (static_branch_likely(&iommu_debug_initialized))
>> 		__iommu_debug_map(domain, phys, size);
>> }
>>
>> (Does it make sense to use static_branch_likely() here? Normally, people
>>   who enable CONFIG_IOMMU_DEBUG_PAGEALLOC would want to use this
>>   debugging feature. Or not?)
>>
>> So that ...
> This actually was the v1 implementation [1], but Jörg suggested to move
> it to a header file as a function call would have an overhead if this
> feautre is disabled.
> 
> I believe the priority would be to keep the performance overhead minimal
> with CONFIG_IOMMU_DEBUG_PAGEALLOC and the commandline disabled, so people
> can run with the config in production and only enable the commandline
> it to debug problems, without having overhead on the typical case.

Okay, fair enough.

Thanks,
baolu

  reply	other threads:[~2025-12-15  3:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 12:59 [PATCH v4 0/4] iommu: Add IOMMU_DEBUG_PAGEALLOC sanitizer Mostafa Saleh
2025-12-11 12:59 ` [PATCH v4 1/4] iommu: Add page_ext for IOMMU_DEBUG_PAGEALLOC Mostafa Saleh
2025-12-12  2:17   ` Baolu Lu
2025-12-12 18:37     ` Mostafa Saleh
2025-12-11 12:59 ` [PATCH v4 2/4] iommu: Add calls " Mostafa Saleh
2025-12-12  2:33   ` Baolu Lu
2025-12-12 18:44     ` Mostafa Saleh
2025-12-15  3:30       ` Baolu Lu [this message]
2025-12-11 12:59 ` [PATCH v4 3/4] iommu: debug-pagealloc: Track IOMMU pages Mostafa Saleh
2025-12-12  2:45   ` Baolu Lu
2025-12-11 12:59 ` [PATCH v4 4/4] iommu: debug-pagealloc: Check mapped/unmapped kernel memory Mostafa Saleh
2025-12-12  2:51   ` Baolu Lu
2025-12-12 18:47     ` Mostafa Saleh

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=7186caa3-13c0-4629-a07f-162c00138ad9@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=iommu@lists.linux.dev \
    --cc=jackmanb@google.com \
    --cc=joro@8bytes.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=rppt@kernel.org \
    --cc=smostafa@google.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=will@kernel.org \
    --cc=xiaqinxin@huawei.com \
    --cc=ziy@nvidia.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).