From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] KVM: Move flags check for user memory regions to the ioctl() specific API
Date: Thu, 8 Aug 2024 15:41:21 +0800 [thread overview]
Message-ID: <0a8fea1b-955e-4a34-91ac-79870c3989d8@intel.com> (raw)
In-Reply-To: <20240802205003.353672-7-seanjc@google.com>
On 8/3/2024 4:50 AM, Sean Christopherson wrote:
> Move the check on memory region flags to kvm_vm_ioctl_set_memory_region()
> now that the internal API, kvm_set_internal_memslot(), disallows any and
> all flags.
>
> No functional change intended.
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> virt/kvm/kvm_main.c | 54 ++++++++++++++++++---------------------------
> 1 file changed, 22 insertions(+), 32 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 84fcb20e3e1c..09cc261b080a 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -1566,34 +1566,6 @@ static void kvm_replace_memslot(struct kvm *kvm,
> #define KVM_SET_USER_MEMORY_REGION_V1_FLAGS \
> (KVM_MEM_LOG_DIRTY_PAGES | KVM_MEM_READONLY)
>
> -static int check_memory_region_flags(struct kvm *kvm,
> - const struct kvm_userspace_memory_region2 *mem)
> -{
> - u32 valid_flags = KVM_MEM_LOG_DIRTY_PAGES;
> -
> - if (kvm_arch_has_private_mem(kvm))
> - valid_flags |= KVM_MEM_GUEST_MEMFD;
> -
> - /* Dirty logging private memory is not currently supported. */
> - if (mem->flags & KVM_MEM_GUEST_MEMFD)
> - valid_flags &= ~KVM_MEM_LOG_DIRTY_PAGES;
> -
> -#ifdef CONFIG_HAVE_KVM_READONLY_MEM
> - /*
> - * GUEST_MEMFD is incompatible with read-only memslots, as writes to
> - * read-only memslots have emulated MMIO, not page fault, semantics,
> - * and KVM doesn't allow emulated MMIO for private memory.
> - */
> - if (!(mem->flags & KVM_MEM_GUEST_MEMFD))
> - valid_flags |= KVM_MEM_READONLY;
> -#endif
> -
> - if (mem->flags & ~valid_flags)
> - return -EINVAL;
> -
> - return 0;
> -}
I would vote for keeping it instead of open coding it.
> -
> static void kvm_swap_active_memslots(struct kvm *kvm, int as_id)
> {
> struct kvm_memslots *slots = kvm_get_inactive_memslots(kvm, as_id);
> @@ -1986,10 +1958,6 @@ static int kvm_set_memory_region(struct kvm *kvm,
>
> lockdep_assert_held(&kvm->slots_lock);
>
> - r = check_memory_region_flags(kvm, mem);
> - if (r)
> - return r;
> -
> as_id = mem->slot >> 16;
> id = (u16)mem->slot;
>
> @@ -2114,6 +2082,28 @@ EXPORT_SYMBOL_GPL(kvm_set_internal_memslot);
> static int kvm_vm_ioctl_set_memory_region(struct kvm *kvm,
> struct kvm_userspace_memory_region2 *mem)
> {
> + u32 valid_flags = KVM_MEM_LOG_DIRTY_PAGES;
> +
> + if (kvm_arch_has_private_mem(kvm))
> + valid_flags |= KVM_MEM_GUEST_MEMFD;
> +
> + /* Dirty logging private memory is not currently supported. */
> + if (mem->flags & KVM_MEM_GUEST_MEMFD)
> + valid_flags &= ~KVM_MEM_LOG_DIRTY_PAGES;
> +
> +#ifdef CONFIG_HAVE_KVM_READONLY_MEM
> + /*
> + * GUEST_MEMFD is incompatible with read-only memslots, as writes to
> + * read-only memslots have emulated MMIO, not page fault, semantics,
> + * and KVM doesn't allow emulated MMIO for private memory.
> + */
> + if (!(mem->flags & KVM_MEM_GUEST_MEMFD))
> + valid_flags |= KVM_MEM_READONLY;
> +#endif
> +
> + if (mem->flags & ~valid_flags)
> + return -EINVAL;
> +
> if ((u16)mem->slot >= KVM_USER_MEM_SLOTS)
> return -EINVAL;
>
prev parent reply other threads:[~2024-08-08 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 20:49 [PATCH 0/6] KVM: kvm_set_memory_region() cleanups Sean Christopherson
2024-08-02 20:49 ` [PATCH 1/6] KVM: Open code kvm_set_memory_region() into its sole caller (ioctl() API) Sean Christopherson
2024-08-05 8:39 ` Tao Su
2024-08-02 20:49 ` [PATCH 2/6] KVM: Assert slots_lock is held in __kvm_set_memory_region() Sean Christopherson
2024-08-05 8:41 ` Tao Su
2024-08-05 22:01 ` Sean Christopherson
2024-08-02 20:50 ` [PATCH 3/6] KVM: Add a dedicated API for setting KVM-internal memslots Sean Christopherson
2024-08-05 8:42 ` Tao Su
2024-08-02 20:50 ` [PATCH 4/6] KVM: x86: Drop double-underscores from __kvm_set_memory_region() Sean Christopherson
2024-08-02 20:50 ` [PATCH 5/6] KVM: Disallow all flags for KVM-internal memslots Sean Christopherson
2024-08-02 20:50 ` [PATCH 6/6] KVM: Move flags check for user memory regions to the ioctl() specific API Sean Christopherson
2024-08-08 7:41 ` Xiaoyao Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a8fea1b-955e-4a34-91ac-79870c3989d8@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®