From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF1513E5ED6; Tue, 17 Mar 2026 19:05:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773774343; cv=none; b=FhaFxk7N+eYDxLw42IvH+vOZ1PbpFV65O0RZem2eqVXg2B430hxhYoo/3l1L4AOUP3espcAWn9svwkC8QOQgkSYoZG133BPxrN4G7n61eW46RAcJPFYhnHUTe/MRoyrrEuBAQ2Sp++YvTzzTDROlCiH6hjp5qtHzMCPrqVszxaw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773774343; c=relaxed/simple; bh=syW3z0x80IUsDkJqDO1sfU4YY8HBrpHtA77ObK08ZFo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Q76V/LLtGIjS2sCJcdINX6Sw0By0nS+Hu6Kkf5jUEnoJmfKa+ZLAkRLO+x/iXpGtBjGDCTe+wGLLse9lX04auWLBhgSuBsYhDBs9NERchuUxOY0tzL/BxylIcdCBveFH+JkPCWBMLseC+DhimqxOpExH55Zrw0nwqryAnOhedck= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=VRWgTDqb; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="VRWgTDqb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A1F64C4CEF7; Tue, 17 Mar 2026 19:05:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773774343; bh=syW3z0x80IUsDkJqDO1sfU4YY8HBrpHtA77ObK08ZFo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=VRWgTDqbWe3Q1W3JoxRORGEv9cJSyULlIC1z8Bw/dttRqK0xrUjV3jcLj+FCNIlhA yfquFZi5RuoGYh094bwpTEqzMSy1oi20VB/mwVmDasAQXUEDUj69QwmFrLNkzzaaEW TxL4IoR2tfqmdocyZECPzry0Flux1xfTuoo78wga02G7HX9CfQP86SEbWHmeki3bnG fQQPAweWzmsOQWPyYRrr1vn+O2GeAM0lXjxVoRUKicNl0fMpfX0u90da1igsahAgWD lVpeDEoTnLCevj3RHVAGT/mI6ZPAnZpFvQykUFfbUgqTYwv27pZul8kECdVX2mxKrW MJpheC1EsGxUQ== Date: Tue, 17 Mar 2026 21:05:38 +0200 From: Leon Romanovsky To: Marek Szyprowski , Robin Murphy , "Michael S. Tsirkin" , Petr Tesarik , Jonathan Corbet , Shuah Khan , Jason Wang , Xuan Zhuo , Eugenio =?iso-8859-1?Q?P=E9rez?= , Jason Gunthorpe , Steven Rostedt , Masami Hiramatsu , Mathieu Desnoyers , Joerg Roedel , Will Deacon , Andrew Morton Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, virtualization@lists.linux.dev, linux-rdma@vger.kernel.org, linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH v3 0/8] RDMA: Enable operation with DMA debug enabled Message-ID: <20260317190538.GD61385@unreal> References: <20260316-dma-debug-overlap-v3-0-1dde90a7f08b@nvidia.com> Precedence: bulk X-Mailing-List: virtualization@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260316-dma-debug-overlap-v3-0-1dde90a7f08b@nvidia.com> On Mon, Mar 16, 2026 at 09:06:44PM +0200, Leon Romanovsky wrote: > Add a new DMA_ATTR_REQUIRE_COHERENT attribute to the DMA API to mark > mappings that must run on a DMA‑coherent system. Such buffers cannot > use the SWIOTLB path, may overlap with CPU caches, and do not depend on > explicit cache flushing. > > Mappings using this attribute are rejected on systems where cache > side‑effects could lead to data corruption, and therefore do not need > the cache‑overlap debugging logic. This series also includes fixes for > DMA_ATTR_CPU_CACHE_CLEAN handling. > Thanks. <...> > --- > Leon Romanovsky (8): > dma-debug: Allow multiple invocations of overlapping entries > dma-mapping: handle DMA_ATTR_CPU_CACHE_CLEAN in trace output > dma-mapping: Clarify valid conditions for CPU cache line overlap > dma-mapping: Introduce DMA require coherency attribute > dma-direct: prevent SWIOTLB path when DMA_ATTR_REQUIRE_COHERENT is set > iommu/dma: add support for DMA_ATTR_REQUIRE_COHERENT attribute > RDMA/umem: Tell DMA mapping that UMEM requires coherency > mm/hmm: Indicate that HMM requires DMA coherency > > Documentation/core-api/dma-attributes.rst | 38 ++++++++++++++++++++++++------- > drivers/infiniband/core/umem.c | 5 ++-- > drivers/iommu/dma-iommu.c | 21 +++++++++++++---- > drivers/virtio/virtio_ring.c | 10 ++++---- > include/linux/dma-mapping.h | 15 ++++++++---- > include/trace/events/dma.h | 4 +++- > kernel/dma/debug.c | 9 ++++---- > kernel/dma/direct.h | 7 +++--- > kernel/dma/mapping.c | 6 +++++ > mm/hmm.c | 4 ++-- > 10 files changed, 86 insertions(+), 33 deletions(-) Marek, Despite the "RDMA ..." tag in the subject, the diffstat clearly shows that you are the appropriate person to take this patch. Thanks. > --- > base-commit: 11439c4635edd669ae435eec308f4ab8a0804808 > change-id: 20260305-dma-debug-overlap-21487c3fa02c > > Best regards, > -- > Leon Romanovsky >