From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Sean Christopherson" <seanjc@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Tao Su" <tao1.su@linux.intel.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Xiaoyao Li" <xiaoyao.li@intel.com>
Subject: Re: [PATCH v2 0/5] KVM: kvm_set_memory_region() cleanups
Date: Mon, 13 Jan 2025 18:30:43 +0100 [thread overview]
Message-ID: <D714H3L41ZMM.1R3UEQ00HD8XG@linux.ibm.com> (raw)
In-Reply-To: <20250111002022.1230573-1-seanjc@google.com>
On Sat Jan 11, 2025 at 1:20 AM CET, Sean Christopherson wrote:
> Cleanups related to kvm_set_memory_region(), salvaged from similar patches
> that were flying around when we were sorting out KVM_SET_USER_MEMORY_REGION2.
>
> And, hopefully, the KVM-internal memslots hardening will also be useful for
> s390's ucontrol stuff (https://lore.kernel.org/all/Z4FJNJ3UND8LSJZz@google.com).
Whole series:
Acked-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
>
> v2:
> - Keep check_memory_region_flags() where it is. [Xiaoyao]
> - Rework the changelog for the last patch to account for the change in
> motiviation.
> - Fix double spaces goofs. [Tao]
> - Add a lockdep assertion in the x86 code, too. [Tao]
>
> v1: https://lore.kernel.org/all/20240802205003.353672-1-seanjc@google.com
>
> Sean Christopherson (5):
> KVM: Open code kvm_set_memory_region() into its sole caller (ioctl()
> API)
> KVM: Assert slots_lock is held when setting memory regions
> KVM: Add a dedicated API for setting KVM-internal memslots
> KVM: x86: Drop double-underscores from __kvm_set_memory_region()
> KVM: Disallow all flags for KVM-internal memslots
>
> arch/x86/kvm/x86.c | 7 ++++---
> include/linux/kvm_host.h | 8 +++-----
> virt/kvm/kvm_main.c | 33 ++++++++++++++-------------------
> 3 files changed, 21 insertions(+), 27 deletions(-)
>
>
> base-commit: 10b2c8a67c4b8ec15f9d07d177f63b563418e948
next prev parent reply other threads:[~2025-01-13 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 0:20 [PATCH v2 0/5] KVM: kvm_set_memory_region() cleanups Sean Christopherson
2025-01-11 0:20 ` [PATCH v2 1/5] KVM: Open code kvm_set_memory_region() into its sole caller (ioctl() API) Sean Christopherson
2025-01-11 0:20 ` [PATCH v2 2/5] KVM: Assert slots_lock is held when setting memory regions Sean Christopherson
2025-01-11 0:20 ` [PATCH v2 3/5] KVM: Add a dedicated API for setting KVM-internal memslots Sean Christopherson
2025-01-20 14:44 ` Christoph Schlameuss
2025-01-21 16:05 ` Sean Christopherson
2025-01-21 16:17 ` Claudio Imbrenda
2025-01-21 19:40 ` Christoph Schlameuss
2025-01-11 0:20 ` [PATCH v2 4/5] KVM: x86: Drop double-underscores from __kvm_set_memory_region() Sean Christopherson
2025-01-11 0:20 ` [PATCH v2 5/5] KVM: Disallow all flags for KVM-internal memslots Sean Christopherson
2025-01-13 11:56 ` [PATCH v2 0/5] KVM: kvm_set_memory_region() cleanups Claudio Imbrenda
2025-01-13 17:30 ` Christoph Schlameuss [this message]
2025-01-14 2:09 ` Xiaoyao Li
2025-01-15 2:58 ` Sean Christopherson
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=D714H3L41ZMM.1R3UEQ00HD8XG@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tao1.su@linux.intel.com \
--cc=xiaoyao.li@intel.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