| From: |
| Dave Jiang <dave.jiang-AT-intel.com> |
| To: |
| linux-cxl-AT-vger.kernel.org, nvdimm-AT-lists.linux.dev |
| Subject: |
| [RFC PATCH 00/12] dax: Add DAX to guest memfd support for KVM |
| Date: |
| Thu, 23 Apr 2026 10:02:07 -0700 |
| Message-ID: |
| <20260423170219.281618-1-dave.jiang@intel.com> |
| Cc: |
| djbw-AT-kernel.org, iweiny-AT-kernel.org, pasha.tatashin-AT-soleen.com, mclapinski-AT-google.com, rppt-AT-kernel.org, joao.m.martins-AT-oracle.com, jic23-AT-kernel.org, gourry-AT-gourry.net, john-AT-groves.net, rick.p.edgecombe-AT-intel.com |
| Archive-link: |
| Article |
This RFC series is created as a proof of concept to connect device DAX to guest
memory by riding on top of guest memfd in order to prove out that device DAX
can be used as guest memory. The series seeks to jump start a discussion on
if there are interests in creating a DAX bridge to utilize CXL memory for guest
memory until the N_PRIVATE implementation by Gregory [1] is available upstream
and DAX users are ready to move to the new scheme. Once there's an established
consensus of interest, we can move the discussion to the best way to implement
the DAX bridge and the future of device DAX as guest.
I did the bare minimal to get the PoC to pass a modified version of KVM gmem
selftest (guest_memfd_test) in order to prove out that DAX can go in the gmem
path. A DAX char dev is created and the fd is passed in user space with
vm_set_user_memory_region2(). The DAX region is passed in as a whole when used
unlike memfd where any size can be passed in to be allocated.
The folks on the cc line are people that Dan Williams has mentioned that may be
of interest to this.
[1]: https://lore.kernel.org/linux-cxl/aeWV1CvP9ImZ3eEG@gourry...
Dave Jiang (12):
dax: rate limit dev_dax_huge_fault() output
dax: Save the kva from memremap
dax: Add fallocate support to device dax
dax: Move dax_pgoff_to_phys() to dax bus to be used by dev dax
dax: Add dax_operations and supporting functions to device dax
dax: Add helper to determine if a 'struct file' supports dax
KVM: guest_memfd: Add setup of daxfd when binding gmem
fs: allow char dev to go through fallocate
dax: Add dax_get_dev_dax() helper function
kvm: Implement dax support for KVM faulting
kvm: Add daxfd support for supported flags
selftest/kvm: Add daxfd support for gmem selftest
arch/x86/kvm/Kconfig | 1 +
arch/x86/kvm/mmu/mmu.c | 48 ++-
drivers/dax/bus.c | 132 ++++++-
drivers/dax/dax-private.h | 8 +
drivers/dax/device.c | 80 +++--
fs/open.c | 3 +-
include/linux/dax.h | 15 +
include/linux/kvm_host.h | 39 +++
include/uapi/linux/kvm.h | 4 +
tools/testing/selftests/kvm/Makefile.kvm | 1 +
.../testing/selftests/kvm/guest_daxfd_test.c | 329 ++++++++++++++++++
virt/kvm/Kconfig | 4 +
virt/kvm/guest_memfd.c | 92 ++++-
virt/kvm/kvm_main.c | 6 +
14 files changed, 711 insertions(+), 51 deletions(-)
create mode 100644 tools/testing/selftests/kvm/guest_daxfd_test.c
base-commit: 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b
--
2.53.0
