Messages in this thread | | | Date | Thu, 5 Jan 2023 12:57:47 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCH RFC v7 02/64] KVM: x86: Add KVM_CAP_UNMAPPED_PRIVATE_MEMORY |
| |
On Wed, Jan 04, 2023 at 11:47:21AM -0600, Michael Roth wrote: > But maybe it's okay to just make KVM_CAP_MEMORY_ATTRIBUTES writeable and > require userspace to negotiate it rather than just tying it to > CONFIG_HAVE_KVM_MEMORY_ATTRIBUTES. Or maybe introducing a new > KVM_SET_SUPPORTED_MEMORY_ATTRIBUTES ioctl to pair with > KVM_GET_SUPPORTED_MEMORY_ATTRIBUTES. It sort of makes sense, since userspace > needs to be prepared to deal with KVM_EXIT_MEMORY_FAULTs relating to these > attributes.
Makes sense.
AFAICT, ofc.
-- Regards/Gruss, Boris.
https://people.kernel.org/tglx/notes-about-netiquette
| |