From: Maxim Levitsky <mlevitsk@redhat.com>
To: kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Jing Zhang <jingzhangos@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvm-riscv@lists.infradead.org, Ingo Molnar <mingo@redhat.com>,
linux-riscv@lists.infradead.org, Joey Gouly <joey.gouly@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Albert Ou <aou@eecs.berkeley.edu>,
kvmarm@lists.linux.dev, Alexander Potapenko <glider@google.com>,
x86@kernel.org, Sean Christopherson <seanjc@google.com>,
Anup Patel <anup@brainfault.org>,
Kunkun Jiang <jiangkunkun@huawei.com>,
Atish Patra <atishp@atishpatra.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH 0/3] KVM: extract lock_all_vcpus/unlock_all_vcpus
Date: Mon, 10 Feb 2025 19:09:14 -0500 [thread overview]
Message-ID: <20250211000917.166856-1-mlevitsk@redhat.com> (raw)
Implement Paolo's suggestion of reusing
sev_lock/unlock_vcpus_for_migration in arm and riscv code
for the purpose of taking vcpu->mutex of all vcpus of a VM.
Because sev_lock/unlock_vcpus_for_migration already have a workaround
for lockdep max lock depth, this fixes the lockdep warnings on arm
which were the inspiration for this refactoring.
This patch series was only compile tested on all 3 architectures.
Best regards,
Maxim Levitsky
Maxim Levitsky (3):
KVM: x86: move sev_lock/unlock_vcpus_for_migration to kvm_main.c
KVM: arm64: switch to using kvm_lock/unlock_all_vcpus
RISC-V: KVM: switch to kvm_lock/unlock_all_vcpus
arch/arm64/include/asm/kvm_host.h | 3 --
arch/arm64/kvm/arch_timer.c | 8 ++--
arch/arm64/kvm/arm.c | 32 -------------
arch/arm64/kvm/vgic/vgic-init.c | 11 +++--
arch/arm64/kvm/vgic/vgic-its.c | 18 +++----
arch/arm64/kvm/vgic/vgic-kvm-device.c | 21 ++++----
arch/riscv/kvm/aia_device.c | 36 ++------------
arch/x86/kvm/svm/sev.c | 65 ++-----------------------
include/linux/kvm_host.h | 6 +++
virt/kvm/kvm_main.c | 69 +++++++++++++++++++++++++++
10 files changed, 115 insertions(+), 154 deletions(-)
--
2.26.3
next reply other threads:[~2025-02-11 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 0:09 Maxim Levitsky [this message]
2025-02-11 0:09 ` [PATCH 1/3] KVM: x86: move sev_lock/unlock_vcpus_for_migration to kvm_main.c Maxim Levitsky
2025-02-11 0:09 ` [PATCH 2/3] KVM: arm64: switch to using kvm_lock/unlock_all_vcpus Maxim Levitsky
2025-02-11 9:24 ` Marc Zyngier
2025-02-11 10:40 ` Paolo Bonzini
2025-02-11 0:09 ` [PATCH 3/3] RISC-V: KVM: switch to kvm_lock/unlock_all_vcpus Maxim Levitsky
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=20250211000917.166856-1-mlevitsk@redhat.com \
--to=mlevitsk@redhat.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jiangkunkun@huawei.com \
--cc=jingzhangos@google.com \
--cc=joey.gouly@arm.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=oliver.upton@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yuzenghui@huawei.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