From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id E1B29C8303C for ; Tue, 8 Jul 2025 15:57:40 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 729956B0095; Tue, 8 Jul 2025 11:57:40 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 701786B0098; Tue, 8 Jul 2025 11:57:40 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 617706B0099; Tue, 8 Jul 2025 11:57:40 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 4F6166B0095 for ; Tue, 8 Jul 2025 11:57:40 -0400 (EDT) Received: from smtpin28.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id F30FDC06B2 for ; Tue, 8 Jul 2025 15:57:39 +0000 (UTC) X-FDA: 83641552638.28.9F4F272 Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) by imf14.hostedemail.com (Postfix) with ESMTP id 1DC95100005 for ; Tue, 8 Jul 2025 15:57:36 +0000 (UTC) Authentication-Results: imf14.hostedemail.com; dkim=pass header.d=samsung.com header.s=mail20170921 header.b=PAX9aPjm; spf=pass (imf14.hostedemail.com: domain of m.szyprowski@samsung.com designates 210.118.77.11 as permitted sender) smtp.mailfrom=m.szyprowski@samsung.com; dmarc=pass (policy=none) header.from=samsung.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1751990258; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=uyab8dr49wEubYW85hrXKyGCcYl1OC56FE0kAT8DEIc=; b=kCZlNH3A2XTF97PIuwn1Ycahmc3c7NQpIVhCOJoD5r8WVhdM3DPIF25Yi5Nj37Z/6pI62f HPU+7lGoHNYFCNF6GGKrYc5wAD5LXbFE6+cqkqcnHW5j+mgT5toPwQPKqYlQZNMx8UWQnl 9kIew3tZs9ocaV1eKoT+2fwywCz/paE= ARC-Authentication-Results: i=1; imf14.hostedemail.com; dkim=pass header.d=samsung.com header.s=mail20170921 header.b=PAX9aPjm; spf=pass (imf14.hostedemail.com: domain of m.szyprowski@samsung.com designates 210.118.77.11 as permitted sender) smtp.mailfrom=m.szyprowski@samsung.com; dmarc=pass (policy=none) header.from=samsung.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1751990258; a=rsa-sha256; cv=none; b=E99kaTjjZ7G9H31UVLrAIGdzfp7sTbGZHy6LOqJASRvwYkS74MzXPgfA6aVejatEtDkUWk GqtTilYlUHfM+1SENyThvfBP9kFlpPWdLdF3qx6o05uDmQD3XlQkSZet86LS5BJhue+SEx ThFvk+B550Pc1qH/Nfm5+fwEd+ivW4s= Received: from eucas1p2.samsung.com (unknown [182.198.249.207]) by mailout1.w1.samsung.com (KnoxPortal) with ESMTP id 20250708155734euoutp0163686dfb898135ce5d93852c371e2c17~QUdqtmSG42036120361euoutp01F for ; Tue, 8 Jul 2025 15:57:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20250708155734euoutp0163686dfb898135ce5d93852c371e2c17~QUdqtmSG42036120361euoutp01F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1751990254; bh=uyab8dr49wEubYW85hrXKyGCcYl1OC56FE0kAT8DEIc=; h=Date:Subject:From:To:Cc:In-Reply-To:References:From; b=PAX9aPjmQKMw6GLmeGQtiXElLQtSpy3YzZ/VZyQdgAMom5kiPE/FjvCg3WC/1+nPy 10u5WabCCNOfLJhq7QAU3B1PpRxFQR3S//A+2qstDRiCAC24ehoVJf28O8MpDNi/Zp 1CxnqxNQY3PzCfWVombnnMFfy4sDHCYVZ/YIErc0= Received: from eusmtip2.samsung.com (unknown [203.254.199.222]) by eucas1p1.samsung.com (KnoxPortal) with ESMTPA id 20250708155734eucas1p1407185657d9833058c6b35d11e1d0b01~QUdqUADk60849108491eucas1p1v; Tue, 8 Jul 2025 15:57:34 +0000 (GMT) Received: from [106.210.134.192] (unknown [106.210.134.192]) by eusmtip2.samsung.com (KnoxPortal) with ESMTPA id 20250708155731eusmtip2162f9813a1cd05daa31b4d62d2bead82~QUdnRS2nc2073620736eusmtip2d; Tue, 8 Jul 2025 15:57:30 +0000 (GMT) Message-ID: Date: Tue, 8 Jul 2025 17:57:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/8] dma-mapping: migrate to physical address-based API From: Marek Szyprowski To: Leon Romanovsky Cc: Christoph Hellwig , Jonathan Corbet , Madhavan Srinivasan , Michael Ellerman , Nicholas Piggin , Christophe Leroy , Robin Murphy , Joerg Roedel , Will Deacon , "Michael S. Tsirkin" , Jason Wang , Xuan Zhuo , =?UTF-8?Q?Eugenio_P=C3=A9rez?= , Alexander Potapenko , Marco Elver , Dmitry Vyukov , Masami Hiramatsu , Mathieu Desnoyers , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , Andrew Morton , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, iommu@lists.linux.dev, virtualization@lists.linux.dev, kasan-dev@googlegroups.com, linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org, Jason Gunthorpe Content-Language: en-US In-Reply-To: <39d43309-9f34-48bc-a9ad-108c607ba175@samsung.com> Content-Transfer-Encoding: 8bit X-CMS-MailID: 20250708155734eucas1p1407185657d9833058c6b35d11e1d0b01 X-Msg-Generator: CA Content-Type: text/plain; charset="utf-8" X-RootMTR: 20250625131920eucas1p271b196cde042bd39ac08fb12beff5baf X-EPHeader: CA X-CMS-RootMailID: 20250625131920eucas1p271b196cde042bd39ac08fb12beff5baf References: <35df6f2a-0010-41fe-b490-f52693fe4778@samsung.com> <20250627170213.GL17401@unreal> <20250630133839.GA26981@lst.de> <69b177dc-c149-40d3-bbde-3f6bad0efd0e@samsung.com> <20250708110007.GF592765@unreal> <261f2417-78a9-45b8-bcec-7e36421a243c@samsung.com> <20250708120647.GG592765@unreal> <39d43309-9f34-48bc-a9ad-108c607ba175@samsung.com> X-Rspamd-Queue-Id: 1DC95100005 X-Stat-Signature: 8ttpfrwrizpcsgs16uw3n6fody81bfuk X-Rspam-User: X-Rspamd-Server: rspam07 X-HE-Tag: 1751990256-971680 X-HE-Meta: U2FsdGVkX192XosKxpBo0oMXEjjodbWLgcoEtupj5CUMURJAo6eMSTSIkmBK4zLI9KbgSbcue2LMEfnKY1TIqdeG1ZXbBNNyYTSLuSvNHUkyMSxuZinpPrOUSNgvn4wubULEWRVnXh443Mjwj0pZgPh62Tvl5qpApwpVrtuNsvpvajXBZpF6hlFXnQkZDw1+SprWipCuqtx13a1bWozaPuw1sIjoapsBAgVlVQWfoTs9/lLTeAo1rEcDDa0931f8fY5P5UON7j779qcOpFb8DcMTmfDmAc7k5iCVZ+yAEto1+hI6v8HDAU8C538FZDQswV6UHGVWkEcRdI7o75KjQryVLMjVGzn4NmzI1YK7Dca5P028u++LvnwsOeSWkZY5XEro1KGj31c7eyyhNUojcpW1FjMxWpATbuXKSF6A/FU7H1/vZePsi07SDdobAtbJ+IojzFojFSD7lEdBD0n27mbw+nag9rifK2X3w7oTDlZ8PQaupVoT4gWeUu0yHDKVfZgWUg62agKgDrvFm6GaySqS+iSPNVFi3a75nVQSWksHaLnQYWDk/U9rtxUPkrGWq85HZMVuuwaRRKUutmsvzLzfL1xSavJWE7JpxLkHg3YIiWnLMnqkFWEd2o13FsOtLfvHa+7yg6WZtEn5rNWXDfQsjZ/6U5hS4XQ0IF/Rqb6azKHJpiAWNVH2YnuaRTGMY90YwU3CP3nF8y5gobHCGLeip04VT3exGIDKJIMkdcV3cX4li5eCJz1/01t5GqifqtM9WOAuws9a95dKU3Ynl421Uorcg3sCfiYjpejbnIHuGIjrDbS5KtfzAxys+LIyiyQFuJymBrBGJH7eRbMqp5KIrSnVXu2waSblEG4VFpIIFtkpmX0Eg6LR/Ln8QrgFLbSQGRIV9NDa0INpNpRkMAfuGJ2pkVeRwK7+QXx2B5l8mtnFtgEt5PQ50t8+i5x9WsX2POg32NhkOj07cbS F2C5K7hv mgYrDkJtpVhC8Wz5XMd3QY6izixDlFCz3QGSo+lDWIXFtNorfnBk6ps70HKjKRsmYysQczpd1YtcKhWvlmXWyGmzhrej235PlUDgf0Ys0T0nwRH0DArkWd+84DGOx3SC0M3ov X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On 08.07.2025 14:56, Marek Szyprowski wrote: > On 08.07.2025 14:06, Leon Romanovsky wrote: >> On Tue, Jul 08, 2025 at 01:45:20PM +0200, Marek Szyprowski wrote: >>> On 08.07.2025 13:00, Leon Romanovsky wrote: >>>> On Tue, Jul 08, 2025 at 12:27:09PM +0200, Marek Szyprowski wrote: >>>>> On 30.06.2025 15:38, Christoph Hellwig wrote: >>>>>> On Fri, Jun 27, 2025 at 08:02:13PM +0300, Leon Romanovsky wrote: >>>>>>>> Thanks for this rework! I assume that the next step is to add >>>>>>>> map_phys >>>>>>>> callback also to the dma_map_ops and teach various dma-mapping >>>>>>>> providers >>>>>>>> to use it to avoid more phys-to-page-to-phys conversions. >>>>>>> Probably Christoph will say yes, however I personally don't see any >>>>>>> benefit in this. Maybe I wrong here, but all existing .map_page() >>>>>>> implementation platforms don't support p2p anyway. They won't >>>>>>> benefit >>>>>>> from this such conversion. >>>>>> I think that conversion should eventually happen, and rather >>>>>> sooner than >>>>>> later. >>>>> Agreed. >>>>> >>>>> Applied patches 1-7 to my dma-mapping-next branch. Let me know if one >>>>> needs a stable branch with it. >>>> Thanks a lot, I don't think that stable branch is needed. >>>> Realistically >>>> speaking, my VFIO DMA work won't be merged this cycle, We are in -rc5, >>>> it is complete rewrite from RFC version and touches pci-p2p code (to >>>> remove dependency on struct page) in addition to VFIO, so it will take >>>> time. >>>> >>>> Regarding, last patch (hmm), it will be great if you can take it. >>>> We didn't touch anything in hmm.c this cycle and have no plans to >>>> send PR. >>>> It can safely go through your tree. >>> Okay, then I would like to get an explicit ack from Jérôme for this. >> Jerome is not active in HMM world for a long time already. >> HMM tree is managed by us (RDMA) >> https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=hmm >> ➜  kernel git:(m/dmabuf-vfio) git log --merges mm/hmm.c >> ... >> Pull HMM updates from Jason Gunthorpe: >> ... >> >> https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=58ba80c4740212c29a1cf9b48f588e60a7612209 >> >> +hmm        git >> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git#hmm >> >> We just never bothered to reflect current situation in MAINTAINERS file. > > Maybe this is the time to update it :) > > I was just a bit confused that no-one commented the HMM patch, but if > You maintain it, then this is okay. I've applied the last patch to dma-mapping-for-next branch. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland