On 20.01.25 21:19, Peter Xu wrote:
On Mon, Jan 20, 2025 at 07:47:18PM +0100, David Hildenbrand wrote:
"memory_attribute_manager" is weird if it is not memory, but memory-mapped
I/O ... :)
What you said sounds like a better name already than GuestMemfdManager in
this patch..
Agreed.
:) To me it's ok to call MMIO as part of "memory" too, and
"attribute" can describe the shareable / private (as an attribute). I'm
guessing Yilun and Chenyi will figure that out..
Yes, calling it "attributes" popped up during RFC discussion: in theory,
disacard vs. populated and shared vs. private could co-exist (maybe in
the future with virtio-mem or something similar).
--
Cheers,
David / dhildenb
