From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 32A1936606A; Tue, 26 May 2026 15:34:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779809653; cv=none; b=tabzv/1YPvVXhPR3WCWKKRrPGMb35Zj55jW/3IeZYWtDC5xDKkaJ7X5iEzK6xEH2dVvovuyl5yv8qXeZZvoHeI2ekDFHpWYVr10rXnKORAVomFpHwcPbW1n+DnWp0G+8TABjT189+DbAlNu3cusfRsdLSN0lWvNmHyVGFjF3ZC8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779809653; c=relaxed/simple; bh=IXtklErhcuWlv2r8L97+xvorQ7UpGoL4ZF+VJDkPygU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=E3CnugtlZFvtCBTXXbD3CflRj7qiWhsGfTb6LmaWd9PuRWwGWgRMquZNmxHV5/qybpyXUJ+07uBE4tw6xl3tJZs49rcnyzegA13N8sA1S8sPvZRDIcmqoz6Rya8hm23Pq2nZ159gBFlc4R29uo+u9ixZM8v44mUkAWkxaBqqtRA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Noq6FzjX; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Noq6FzjX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A5FAF1F00A3C; Tue, 26 May 2026 15:33:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779809651; bh=IXtklErhcuWlv2r8L97+xvorQ7UpGoL4ZF+VJDkPygU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Noq6FzjXAHednyJbKDsO7gWlmRYH4wZD0QhvuTN+ag2i1VdurKmvBGP3bOfMJCqvU 8kjwZvotf99uxGidiSuhzx7jYl16j0j9D5Yy+Ia0rEVFPucuDOg4YzNa4k3kD5Caql cOvHKMZEdCkn6xBAgqAbnQEdTy1mWt1ZyuPL6nPS3yKF2BtW7gtEowzkU10F/6E0sj qQ72PTZCTU8zRN6nz5ooPdaaDrJoW5P+Y3vgo8M1qA9dygwm5nF6SDZ5t2jHBQrPRo Mw4mppN1KUMAVp0SjeJl63QoEfTyTcLoZY3AGxngefu9qBzd2UnGgPGypTmdUHd5W5 d3hKUeNpi6bxA== Date: Tue, 26 May 2026 16:33:56 +0100 From: Lorenzo Stoakes To: Yin Tirui Cc: Andrew Morton , Matthew Wilcox , David Hildenbrand , Juergen Gross , Jonathan Cameron , Will Deacon , Catalin Marinas , Peter Xu , Luiz Capitulino , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H . Peter Anvin" , Andy Lutomirski , Peter Zijlstra , Madhavan Srinivasan , Michael Ellerman , Nicholas Piggin , Christophe Leroy , "Liam R . Howlett" , Zi Yan , Baolin Wang , Nico Pache , Ryan Roberts , Dev Jain , Barry Song , Lance Yang , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Anshuman Khandual , Rohan McLure , Kevin Brodsky , Alistair Popple , Andrew Donnellan , Pasha Tatashin , Baoquan He , Thomas Huth , Coiby Xu , Dan Williams , Yu-cheng Yu , Lu Baolu , Conor Dooley , Rik van Riel , wangkefeng.wang@huawei.com, chenjun102@huawei.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, x86@kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-pm@vger.kernel.org Subject: Re: [PATCH mm-unstable RFC v4 0/7] mm: add huge pfnmap support for remap_pfn_range() Message-ID: References: <20260526145003.88445-1-yintirui@huawei.com> Precedence: bulk X-Mailing-List: linux-pm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260526145003.88445-1-yintirui@huawei.com> Allow me to be mildly pedantic (sorry :) One thing I'd like to highlight here is that remap_pfn_range() is, in the long run, deprecated. mmap_prepare callbacks will indicate a PFN remap mmap_action, which will do the heavy lifting (see [0]). So perhaps worth referring to 'PFN remapping' or something? (Since we already have mmap_prepare() in use, it's also kinda inaccurate to say remap_pfn_range() :) [0]: https://www.kernel.org/doc/html/next/filesystems/mmap_prepare.html Sorry, this is pretty nitpicky :) Cheers, Lorenzo