Linux Confidential Computing Development
 help / color / mirror / Atom feed
 messages from 2026-11-01 07:19:43 to 2026-11-01 07:28:58 UTC [more...]

[RFC PATCH v2 00/13] KVM/VFIO: guest_memfd support for device MMIO resources
 2026-11-01  7:28 UTC  (5+ messages)
` [RFC PATCH v2 02/13] KVM: guest_memfd: Support private/shared conversion of device memory

[RFC PATCH v3 00/13] KVM: guest_memfd: Add a common framework for device memory providers
 2026-11-01  7:19 UTC  (14+ messages)
` [RFC PATCH v3 01/13] KVM: guest_memfd: Let providers prepare memory regions
` [RFC PATCH v3 02/13] KVM: guest_memfd: Dispatch attribute conversion through backing operations
` [RFC PATCH v3 03/13] KVM: guest_memfd: Let providers coordinate mapping changes
` [RFC PATCH v3 04/13] KVM: guest_memfd: Dispatch revocation through backing operations
` [RFC PATCH v3 05/13] KVM: guest_memfd: Split population by backing type
` [RFC PATCH v3 06/13] KVM: guest_memfd: Support device-backed PFN providers
` [RFC PATCH v3 07/13] KVM: guest_memfd: Support private/shared conversion of device memory
` [RFC PATCH v3 08/13] KVM: guest_memfd: Track private device ranges after attribute updates
` [RFC PATCH v3 09/13] KVM: guest_memfd: Expose device provider private state
` [RFC PATCH v3 10/13] KVM: guest_memfd: Support range revocation of device mappings
` [RFC PATCH v3 11/13] KVM: guest_memfd: Add shared device mmap through PFN providers
` [RFC PATCH v3 12/13] KVM: guest_memfd: Remove device mappings on final close
` [RFC PATCH v3 13/13] KVM: guest_memfd: Invalidate guest_memfd mappings before removing memslot bindings


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox