RFC dax: Add DAX to guest memfd support for KVM
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest12 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/12 | dax: rate limit dev_dax_huge_fault() outputdrivers/ | +5 | 0 replies | |
| 2/12 | dax: Save the kva from memremapdrivers/ drivers/ | +23 | 0 replies | |
| 3/12 | dax: Add fallocate support to device daxdrivers/ | +29 | 0 replies | |
| 4/12 | dax: Move dax_pgoff_to_phys() to dax bus to be used by dev daxdrivers/ drivers/ | +24 | 0 replies | |
| 5/12 | dax: Add dax_operations and supporting functions to device daxdrivers/ | +97 | 0 replies | |
| 6/12 | dax: Add helper to determine if a 'struct file' supports daxinclude/ | +7 | 0 replies | |
| 7/12 | KVM: guest_memfd: Add setup of daxfd when binding gmemarch/ drivers/ drivers/ +3 more | +70 | 0 replies | |
| 8/12 | fs: allow char dev to go through fallocatefs/ | +2 | 0 replies | |
| 9/12 | dax: Add dax_get_dev_dax() helper functiondrivers/ include/ | +13 | 0 replies | |
| 10/12 | kvm: Implement dax support for KVM faultingarch/ drivers/ include/ +2 more | +94 | 0 replies | |
| 11/12 | kvm: Add daxfd support for supported flagsinclude/ include/ virt/ | +17 | 0 replies | |
| 12/12 | selftest/kvm: Add daxfd support for gmem selftesttools/ tools/ | +330 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 00/12] dax: Add DAX to guest memfd support for KVM
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-fedora-PF4VCD3F/T/#t
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
Signature · 1 line
2.53.0