Thread (83 messages) 83 messages, 11 authors, 2026-02-05

Re: [RFC PATCH v1 05/37] KVM: guest_memfd: Wire up kvm_get_memory_attributes() to per-gmem attributes

From: Xu Yilun <hidden>
Date: 2026-02-05 07:23:46
Also in: cgroups, kvm, linux-doc, linux-fsdevel, linux-kselftest, linux-trace-kernel, lkml

On Wed, Feb 04, 2026 at 08:47:15AM -0400, Jason Gunthorpe wrote:
On Wed, Feb 04, 2026 at 12:43:16PM +0800, Xu Yilun wrote:
quoted
quoted
Which means we need VFIO to know what they are, and hopefully it is
just static based on the TDISP reports..
I don't think VMM need to check TDISP report. The only special thing is
the MSI-X mixed pages which can be figured out by standard PCI
discovery.
Either that or follow along with the guests's choices on
shared/private.

We can't let VFIO mmap a private MMIO page, so it has to know which
pages are private at any moment, and it can't guess.
No we could only let VFIO mmap MMIO pages that need emulation (like this
MSI-X mixed page). MMIOs in such page cannot be assigned to guest so no
way to convert to private.

We don't allow VFIO mmap all asigned MMIO pages, no matter they will be
private or shared. They are assigned to guest, so host don't touch them.
Does that make sense?
Jason
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help