|
From: | Xiaoyao Li |
Subject: | Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory |
Date: | Tue, 13 Dec 2022 20:04:14 +0800 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.5.1 |
On 12/8/2022 7:30 PM, Chao Peng wrote:
On Thu, Dec 08, 2022 at 04:37:03PM +0800, Xiaoyao Li wrote:On 12/2/2022 2:13 PM, Chao Peng wrote: ..Together with the change, a new config HAVE_KVM_RESTRICTED_MEM is added and right now it is selected on X86_64 only.From the patch implementation, I have no idea why HAVE_KVM_RESTRICTED_MEM is needed.The reason is we want KVM further controls the feature enabling. An opt-in CONFIG_RESTRICTEDMEM can cause problem if user sets that for unsupported architectures.
HAVE_KVM_RESTRICTED_MEM is not used in this patch. It's better to introduce it in the patch that actually uses it.
Here is the original discussion: https://lore.kernel.org/all/YkJLFu98hZOvTSrL@google.com/ Thanks, Chao
[Prev in Thread] | Current Thread | [Next in Thread] |