Re: [RFC PATCH v2 02/21] RAMBlock: Add support of KVM private gmem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 22.09.23 02:22, Xiaoyao Li wrote:
On 9/21/2023 4:55 PM, David Hildenbrand wrote:
On 14.09.23 05:50, Xiaoyao Li wrote:
From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>

Add KVM gmem support to RAMBlock so both normal hva based memory
and kvm gmem fd based private memory can be associated in one RAMBlock.

Introduce new flag RAM_KVM_GMEM. It calls KVM ioctl to create private
gmem for the RAMBlock when it's set.


But who sets RAM_KVM_GMEM and when?

The answer is in the next patch. When `private` property of memory
backend is set to true, it will pass RAM_KVM_GMEM flag to
memory_region_init_ram_*()

Okay, assuming that patch (and property) will go away, I assume this flag can also go away, right?

--
Cheers,

David / dhildenb




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux