From: mlevitsk@redhat.com
To: kvm@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Will Deacon <will@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Kunkun Jiang <jiangkunkun@huawei.com>,
Jing Zhang <jingzhangos@google.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Keisuke Nishimura <keisuke.nishimura@inria.fr>,
Anup Patel <anup@brainfault.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Atish Patra <atishp@atishpatra.org>,
kvmarm@lists.linux.dev, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Sebastian Ott <sebott@redhat.com>,
Andre Przywara <andre.przywara@arm.com>,
Ingo Molnar <mingo@redhat.com>, Alexandre Ghiti <alex@ghiti.fr>,
Bjorn Helgaas <bhelgaas@google.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Joey Gouly <joey.gouly@arm.com>, Borislav Petkov <bp@alien8.de>,
Sean Christopherson <seanjc@google.com>,
Marc Zyngier <maz@kernel.org>,
Alexander Potapenko <glider@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Shusen Li <lishusen2@huawei.com>,
kvm-riscv@lists.infradead.org
Subject: Re: [PATCH v3 0/4] KVM: lockdep improvements
Date: Wed, 30 Apr 2025 16:30:51 -0400 [thread overview]
Message-ID: <53a26378fce90c8bbfa57a582992324560aa0274.camel@redhat.com> (raw)
In-Reply-To: <20250430202311.364641-1-mlevitsk@redhat.com>
On Wed, 2025-04-30 at 16:23 -0400, Maxim Levitsky wrote:
> This is a continuation of my 'extract
> lock_all_vcpus/unlock_all_vcpus'
> patch series.
>
> Implement the suggestion of using lockdep's "nest_lock" feature
> when locking all KVM vCPUs by adding mutex_trylock_nest_lock() and
> mutex_lock_killable_nest_lock() and use these functions in the
> implementation of the
> kvm_trylock_all_vcpus()/kvm_lock_all_vcpus()/kvm_unlock_all_vcpus().
>
> Those changes allow removal of a custom workaround that was needed to
> silence the lockdep warning in the SEV code and also stop lockdep
> from
> complaining in case of ARM and RISC-V code which doesn't include the
> above
> mentioned workaround.
>
> Finally, it's worth noting that this patch series removes a fair
> amount of duplicate code by implementing the logic in one place.
>
> Best regards,
> Maxim Levitsky
>
> Maxim Levitsky (4):
> arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs
> RISC-V: KVM: switch to kvm_lock/unlock_all_vcpus
> locking/mutex: implement mutex_lock_killable_nest_lock
> x86: KVM: SEV: implement kvm_lock_all_vcpus and use it
>
> arch/arm64/include/asm/kvm_host.h | 3 --
> arch/arm64/kvm/arch_timer.c | 4 +-
> arch/arm64/kvm/arm.c | 43 ----------------
> arch/arm64/kvm/vgic/vgic-init.c | 4 +-
> arch/arm64/kvm/vgic/vgic-its.c | 8 +--
> arch/arm64/kvm/vgic/vgic-kvm-device.c | 12 ++---
> arch/riscv/kvm/aia_device.c | 34 +------------
> arch/x86/kvm/svm/sev.c | 72 ++-----------------------
> --
> include/linux/kvm_host.h | 4 ++
> include/linux/mutex.h | 17 +++++--
> kernel/locking/mutex.c | 7 +--
> virt/kvm/kvm_main.c | 59 ++++++++++++++++++++++
> 12 files changed, 100 insertions(+), 167 deletions(-)
>
> --
> 2.46.0
>
>
I forgot to send first patch in the series, resending.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2025-04-30 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:23 [PATCH v3 0/4] KVM: lockdep improvements Maxim Levitsky
2025-04-30 20:23 ` [PATCH v3 1/4] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs Maxim Levitsky
2025-05-07 17:04 ` kernel test robot
2025-04-30 20:23 ` [PATCH v3 2/4] RISC-V: KVM: switch to kvm_lock/unlock_all_vcpus Maxim Levitsky
2025-04-30 20:23 ` [PATCH v3 3/4] locking/mutex: implement mutex_lock_killable_nest_lock Maxim Levitsky
2025-04-30 20:23 ` [PATCH v3 4/4] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it Maxim Levitsky
2025-04-30 20:30 ` mlevitsk [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=53a26378fce90c8bbfa57a582992324560aa0274.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=alex@ghiti.fr \
--cc=andre.przywara@arm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=bhelgaas@google.com \
--cc=boqun.feng@gmail.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=keisuke.nishimura@inria.fr \
--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=lishusen2@huawei.com \
--cc=longman@redhat.com \
--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=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=seanjc@google.com \
--cc=sebott@redhat.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