From: Michael Kelley <mhklinux@outlook.com>
To: Alistair Popple <apopple@nvidia.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "gerald.schaefer@linux.ibm.com" <gerald.schaefer@linux.ibm.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"willy@infradead.org" <willy@infradead.org>,
"david@redhat.com" <david@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"jhubbard@nvidia.com" <jhubbard@nvidia.com>,
"hch@lst.de" <hch@lst.de>,
"zhang.lyra@gmail.com" <zhang.lyra@gmail.com>,
"debug@rivosinc.com" <debug@rivosinc.com>,
"bjorn@kernel.org" <bjorn@kernel.org>,
"balbirs@nvidia.com" <balbirs@nvidia.com>,
"lorenzo.stoakes@oracle.com" <lorenzo.stoakes@oracle.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"loongarch@lists.linux.dev" <loongarch@lists.linux.dev>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"John@Groves.net" <John@Groves.net>
Subject: RE: [PATCH 11/12] mm: Remove callers of pfn_t functionality
Date: Mon, 2 Jun 2025 04:44:06 +0000 [thread overview]
Message-ID: <SN6PR02MB4157F8C860B0164C4115622CD462A@SN6PR02MB4157.namprd02.prod.outlook.com> (raw)
In-Reply-To: <4b644a3562d1b4679f5c4a042d8b7d565e24c470.1748500293.git-series.apopple@nvidia.com>
From: Alistair Popple <apopple@nvidia.com> Sent: Wednesday, May 28, 2025 11:32 PM
>
> All PFN_* pfn_t flags have been removed. Therefore there is no longer
> a need for the pfn_t type and all uses can be replaced with normal
> pfns.
>
> Signed-off-by: Alistair Popple <apopple@nvidia.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
> arch/x86/mm/pat/memtype.c | 6 +-
> drivers/dax/device.c | 23 +++----
> drivers/dax/hmem/hmem.c | 1 +-
> drivers/dax/kmem.c | 1 +-
> drivers/dax/pmem.c | 1 +-
> drivers/dax/super.c | 3 +-
> drivers/gpu/drm/exynos/exynos_drm_gem.c | 1 +-
> drivers/gpu/drm/gma500/fbdev.c | 3 +-
> drivers/gpu/drm/i915/gem/i915_gem_mman.c | 1 +-
> drivers/gpu/drm/msm/msm_gem.c | 1 +-
> drivers/gpu/drm/omapdrm/omap_gem.c | 6 +--
> drivers/gpu/drm/v3d/v3d_bo.c | 1 +-
> drivers/hwtracing/intel_th/msu.c | 3 +-
> drivers/md/dm-linear.c | 2 +-
> drivers/md/dm-log-writes.c | 2 +-
> drivers/md/dm-stripe.c | 2 +-
> drivers/md/dm-target.c | 2 +-
> drivers/md/dm-writecache.c | 11 +--
> drivers/md/dm.c | 2 +-
> drivers/nvdimm/pmem.c | 8 +--
> drivers/nvdimm/pmem.h | 4 +-
> drivers/s390/block/dcssblk.c | 9 +--
> drivers/vfio/pci/vfio_pci_core.c | 5 +-
> fs/cramfs/inode.c | 5 +-
> fs/dax.c | 50 +++++++--------
> fs/ext4/file.c | 2 +-
> fs/fuse/dax.c | 3 +-
> fs/fuse/virtio_fs.c | 5 +-
> fs/xfs/xfs_file.c | 2 +-
> include/linux/dax.h | 9 +--
> include/linux/device-mapper.h | 2 +-
> include/linux/huge_mm.h | 6 +-
> include/linux/mm.h | 4 +-
> include/linux/pfn.h | 9 +---
> include/linux/pfn_t.h | 85 +-------------------------
> include/linux/pgtable.h | 4 +-
> include/trace/events/fs_dax.h | 12 +---
> mm/debug_vm_pgtable.c | 1 +-
> mm/huge_memory.c | 27 +++-----
> mm/memory.c | 31 ++++-----
> mm/memremap.c | 1 +-
> mm/migrate.c | 1 +-
> tools/testing/nvdimm/pmem-dax.c | 6 +-
> tools/testing/nvdimm/test/iomap.c | 7 +--
> tools/testing/nvdimm/test/nfit_test.h | 1 +-
> 45 files changed, 121 insertions(+), 250 deletions(-)
> delete mode 100644 include/linux/pfn_t.h
>
[snip]
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index c5345ee..12d9665 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -3644,9 +3644,9 @@ vm_fault_t vmf_insert_pfn(struct vm_area_struct *vma, unsigned long addr,
> vm_fault_t vmf_insert_pfn_prot(struct vm_area_struct *vma, unsigned long addr,
> unsigned long pfn, pgprot_t pgprot);
> vm_fault_t vmf_insert_mixed(struct vm_area_struct *vma, unsigned long addr,
> - pfn_t pfn);
> + unsigned long pfn);
> vm_fault_t vmf_insert_mixed_mkwrite(struct vm_area_struct *vma,
> - unsigned long addr, pfn_t pfn);
> + unsigned long addr, unsigned long pfn);
> int vm_iomap_memory(struct vm_area_struct *vma, phys_addr_t start, unsigned long len);
>
> static inline vm_fault_t vmf_insert_page(struct vm_area_struct *vma,
[snip]
> diff --git a/mm/memory.c b/mm/memory.c
> index 6b03771..4eaf444 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -2635,7 +2634,7 @@ EXPORT_SYMBOL(vmf_insert_mixed);
> * the same entry was actually inserted.
> */
> vm_fault_t vmf_insert_mixed_mkwrite(struct vm_area_struct *vma,
> - unsigned long addr, pfn_t pfn)
> + unsigned long addr, unsigned long pfn)
> {
> return __vm_insert_mixed(vma, addr, pfn, true);
> }
vmf_insert_mixed_mkwrite() is not used anywhere in the
kernel. The commit message for cd1e0dac3a3e suggests it was
originally used by DAX code, so presumably it could just go away.
On the flip side, I have a patch set in flight (see Patch 3 of [1])
that uses it to do mkwrite on a special PTE, and my usage
requires passing PFN_SPECIAL in order to pass the tests in
vm_mixed_ok(). But this may be dubious usage, and should not
be a blocker to your elimination of pfn_t. I'll either add
vmf_insert_special_mkwrite() or figure out an equivalent. Anyone
with suggestions in that direction would be appreciated as I'm
not an mm expert.
Michael
[1] https://lore.kernel.org/linux-hyperv/20250523161522.409504-1-mhklinux@outlook.com/
next prev parent reply other threads:[~2025-06-02 4:44 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 6:32 [PATCH 00/12] mm: Remove pXX_devmap page table bit and pfn_t type Alistair Popple
2025-05-29 6:32 ` [PATCH 01/12] mm: Remove PFN_MAP, PFN_SG_CHAIN and PFN_SG_LAST Alistair Popple
2025-05-29 11:46 ` Jonathan Cameron
2025-06-04 3:22 ` Alistair Popple
2025-05-30 9:33 ` David Hildenbrand
2025-06-02 4:54 ` Christoph Hellwig
2025-06-04 3:23 ` Alistair Popple
2025-06-03 13:34 ` Jason Gunthorpe
2025-06-04 21:05 ` Dan Williams
2025-05-29 6:32 ` [PATCH 02/12] mm: Convert pXd_devmap checks to vma_is_dax Alistair Popple
2025-05-30 9:37 ` David Hildenbrand
2025-06-12 6:55 ` Alistair Popple
2025-06-03 13:35 ` Jason Gunthorpe
2025-06-05 1:37 ` Dan Williams
2025-05-29 6:32 ` [PATCH 03/12] mm/pagewalk: Skip dax pages in pagewalk Alistair Popple
2025-05-30 9:42 ` David Hildenbrand
2025-06-03 13:36 ` Jason Gunthorpe
2025-06-05 1:59 ` Dan Williams
2025-06-05 7:46 ` Christoph Hellwig
2025-06-05 7:49 ` David Hildenbrand
2025-06-05 16:21 ` Dan Williams
2025-06-12 7:02 ` Alistair Popple
2025-06-12 8:47 ` Alistair Popple
2025-06-12 14:15 ` Lorenzo Stoakes
2025-06-12 22:50 ` Alistair Popple
2025-05-29 6:32 ` [PATCH 04/12] mm: Convert vmf_insert_mixed() from using pte_devmap to pte_special Alistair Popple
2025-06-03 13:37 ` Jason Gunthorpe
2025-06-05 2:02 ` Dan Williams
2025-05-29 6:32 ` [PATCH 05/12] mm: Remove remaining uses of PFN_DEV Alistair Popple
2025-06-03 13:38 ` Jason Gunthorpe
2025-06-05 2:02 ` Dan Williams
2025-05-29 6:32 ` [PATCH 06/12] mm/gup: Remove pXX_devmap usage from get_user_pages() Alistair Popple
2025-06-03 13:47 ` Jason Gunthorpe
2025-06-05 2:04 ` Dan Williams
2025-05-29 6:32 ` [PATCH 07/12] mm: Remove redundant pXd_devmap calls Alistair Popple
2025-05-29 11:54 ` Jonathan Cameron
2025-06-02 9:33 ` David Hildenbrand
2025-06-02 12:20 ` David Hildenbrand
2025-06-03 13:48 ` Jason Gunthorpe
2025-06-05 2:35 ` Dan Williams
2025-06-05 12:09 ` Jason Gunthorpe
2025-06-05 12:21 ` David Hildenbrand
2025-06-05 16:30 ` Dan Williams
2025-06-05 17:04 ` David Hildenbrand
2025-06-05 16:22 ` Dan Williams
2025-05-29 6:32 ` [PATCH 08/12] mm/khugepaged: Remove redundant pmd_devmap() check Alistair Popple
2025-06-02 11:45 ` David Hildenbrand
2025-06-03 13:48 ` Jason Gunthorpe
2025-05-29 6:32 ` [PATCH 09/12] powerpc: Remove checks for devmap pages and PMDs/PUDs Alistair Popple
2025-06-03 13:49 ` Jason Gunthorpe
2025-05-29 6:32 ` [PATCH 10/12] mm: Remove devmap related functions and page table bits Alistair Popple
2025-06-03 13:50 ` Jason Gunthorpe
2025-05-29 6:32 ` [PATCH 11/12] mm: Remove callers of pfn_t functionality Alistair Popple
2025-06-02 4:44 ` Michael Kelley [this message]
2025-06-03 13:50 ` Jason Gunthorpe
2025-05-29 6:32 ` [PATCH 12/12] mm/memremap: Remove unused devmap_managed_key Alistair Popple
2025-06-03 13:51 ` Jason Gunthorpe
2025-06-02 10:31 ` [PATCH 00/12] mm: Remove pXX_devmap page table bit and pfn_t type David Hildenbrand
2025-06-05 1:39 ` Dan Williams
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=SN6PR02MB4157F8C860B0164C4115622CD462A@SN6PR02MB4157.namprd02.prod.outlook.com \
--to=mhklinux@outlook.com \
--cc=John@Groves.net \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=bjorn@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=debug@rivosinc.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=lorenzo.stoakes@oracle.com \
--cc=nvdimm@lists.linux.dev \
--cc=willy@infradead.org \
--cc=zhang.lyra@gmail.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