|
From: | David Hildenbrand |
Subject: | Re: [RFC PATCH v2 02/21] RAMBlock: Add support of KVM private gmem |
Date: | Thu, 21 Sep 2023 10:55:52 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 |
On 14.09.23 05:50, Xiaoyao Li wrote:
From: Chao Peng <chao.p.peng@linux.intel.com> 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? Don't we simply allocate it for all RAMBlocks under such special VMs? What's the downside of doing that?
-- Cheers, David / dhildenb
[Prev in Thread] | Current Thread | [Next in Thread] |