From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) (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 A798537BE77 for ; Wed, 18 Mar 2026 08:03:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=210.118.77.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773820986; cv=none; b=V118UX152Dkg1i/41xwUYm7w904ThVXxUnDQIptyRL8hQU89GaE9CncOv4iPcN9QwVd50VNON1UrMmkECYSOvRK33ykTt4VhoDTXy8UqcIMwO0n2HCdCY0m4NGhcjdEnRNflQ7s1zcqszujaV+4cIX22s4YpApifFPzuKmxBkXw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773820986; c=relaxed/simple; bh=KpETAyrs7YIkUM70PUxFjh8e+vMzcwee8eeDvL3R0fo=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:From:In-Reply-To: Content-Type:References; b=rOTZzLZIoL2QTT4L/rs0CAKl+VFB6qFkMpkNOPkooMAV4jD27haGw/Oo2zH+3ZFE/ezgqOA2kRPR3VSLqx78NANxJmv8ZHPg4yVv1sgzx0DZmD7eqeBSxYhTTSfYVACmYGe2TJfkqZGVh3CiXL0+p1Ci3S/gmVvs4oQsXZJL8fs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=samsung.com; spf=pass smtp.mailfrom=samsung.com; dkim=pass (1024-bit key) header.d=samsung.com header.i=@samsung.com header.b=QgHOLe5E; arc=none smtp.client-ip=210.118.77.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=samsung.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=samsung.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=samsung.com header.i=@samsung.com header.b="QgHOLe5E" Received: from eucas1p2.samsung.com (unknown [182.198.249.207]) by mailout1.w1.samsung.com (KnoxPortal) with ESMTP id 20260318080302euoutp01ced9b21262baeaf9a262172e408bb229~d4MkluB-f0174001740euoutp01Y for ; Wed, 18 Mar 2026 08:03:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20260318080302euoutp01ced9b21262baeaf9a262172e408bb229~d4MkluB-f0174001740euoutp01Y DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1773820982; bh=5GOrx/bM09mWS7d4FWSxDkysESa+9H3SzC9X1DevVpM=; h=Date:Subject:To:Cc:From:In-Reply-To:References:From; b=QgHOLe5EykCGGsrBolTj2JuPKhQ1Bki0f6knoOEenxKjutlnI1f1a+IvYzTNANjPB g3MbC1nXSFcfIo0O8YAnngJsBgO+mlGjP/L4WRyaF1fcYTT5wusxKKB3bQtIBpaz+e S5X3ZWGOfil6XUIO2rZg9WqmuiJ2qfPQBkCSac3g= Received: from eusmtip2.samsung.com (unknown [203.254.199.222]) by eucas1p2.samsung.com (KnoxPortal) with ESMTPA id 20260318080302eucas1p2c05885afc838bdc98d55972adc31ab96~d4MkRZpJ60631706317eucas1p2v; Wed, 18 Mar 2026 08:03:02 +0000 (GMT) Received: from [106.210.134.192] (unknown [106.210.134.192]) by eusmtip2.samsung.com (KnoxPortal) with ESMTPA id 20260318080300eusmtip289c1a6818cde8d982e474c8d0c9ee8f6~d4Mi2Bedq1876518765eusmtip2G; Wed, 18 Mar 2026 08:03:00 +0000 (GMT) Message-ID: Date: Wed, 18 Mar 2026 09:03:00 +0100 Precedence: bulk X-Mailing-List: virtualization@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Betterbird (Windows) Subject: Re: [PATCH v3 0/8] RDMA: Enable operation with DMA debug enabled To: Leon Romanovsky , Robin Murphy , "Michael S. Tsirkin" , Petr Tesarik , Jonathan Corbet , Shuah Khan , Jason Wang , Xuan Zhuo , =?UTF-8?Q?Eugenio_P=C3=A9rez?= , 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 Content-Language: en-US From: Marek Szyprowski In-Reply-To: <20260317190538.GD61385@unreal> Content-Transfer-Encoding: 8bit X-CMS-MailID: 20260318080302eucas1p2c05885afc838bdc98d55972adc31ab96 X-Msg-Generator: CA Content-Type: text/plain; charset="utf-8" X-RootMTR: 20260317190552eucas1p28f3e818f88d252b1e4161332be084177 X-EPHeader: CA X-CMS-RootMailID: 20260317190552eucas1p28f3e818f88d252b1e4161332be084177 References: <20260316-dma-debug-overlap-v3-0-1dde90a7f08b@nvidia.com> <20260317190538.GD61385@unreal> Hi Leon, On 17.03.2026 20:05, Leon Romanovsky wrote: > 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. I plan to take the first 2 patches to the dma-mapping-fixes branch (v7.0-rc) and the next to dma-mapping-for-next. Should I also take the RDMA and HMM patches, or do You want a stable branch for merging them via respective subsystem trees? Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland