From: Peter Zijlstra <peterz@infradead.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Maxim Levitsky <mlevitsk@redhat.com>,
kvm@vger.kernel.org, linux-riscv@lists.infradead.org,
Kunkun Jiang <jiangkunkun@huawei.com>,
Waiman Long <longman@redhat.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Boqun Feng <boqun.feng@gmail.com>, Borislav Petkov <bp@alien8.de>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Ghiti <alex@ghiti.fr>,
Alexander Potapenko <glider@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
Andre Przywara <andre.przywara@arm.com>,
x86@kernel.org, Joey Gouly <joey.gouly@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
kvm-riscv@lists.infradead.org,
Atish Patra <atishp@atishpatra.org>,
Ingo Molnar <mingo@redhat.com>,
Jing Zhang <jingzhangos@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
kvmarm@lists.linux.dev, Will Deacon <will@kernel.org>,
Keisuke Nishimura <keisuke.nishimura@inria.fr>,
Sebastian Ott <sebott@redhat.com>,
Shusen Li <lishusen2@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Marc Zyngier <maz@kernel.org>, Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v4 5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it
Date: Sat, 3 May 2025 12:08:20 +0200 [thread overview]
Message-ID: <20250503100820.GF4198@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aBUxqZ6qgfYZLsye@google.com>
On Fri, May 02, 2025 at 01:57:13PM -0700, Sean Christopherson wrote:
> int kvm_lock_all_vcpus(struct kvm *kvm)
> {
> struct kvm_vcpu *vcpu;
> unsigned long i, j;
> int r;
>
> lockdep_assert_held(&kvm->lock);
So I agree that having this assertion here is probably good from a
read-code pov, however, strictly speaking, it is redundant in that:
> kvm_for_each_vcpu(i, vcpu, kvm) {
> r = mutex_lock_killable_nest_lock(&vcpu->mutex, &kvm->lock);
will implicitly assert kvm->lock is held. If you try to use an unheld
lock as nest lock, it will complain loudly :-)
(my inner pendant had to reply, ignore at will :-)
> if (r)
> goto out_unlock;
> }
> return 0;
>
> out_unlock:
> kvm_for_each_vcpu(j, vcpu, kvm) {
> if (i == j)
> break;
> mutex_unlock(&vcpu->mutex);
> }
> return r;
> }
> EXPORT_SYMBOL_GPL(kvm_lock_all_vcpus);
prev parent reply other threads:[~2025-05-03 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:30 [PATCH v4 0/5] KVM: lockdep improvements Maxim Levitsky
2025-04-30 20:30 ` [PATCH v4 1/5] locking/mutex: implement mutex_trylock_nested Maxim Levitsky
2025-04-30 20:30 ` [PATCH v4 2/5] arm64: KVM: use mutex_trylock_nest_lock when locking all vCPUs Maxim Levitsky
2025-05-01 8:24 ` Marc Zyngier
2025-05-01 11:15 ` Peter Zijlstra
2025-05-01 12:44 ` Marc Zyngier
2025-05-01 13:41 ` Peter Zijlstra
2025-05-01 13:55 ` Marc Zyngier
2025-05-02 20:58 ` Sean Christopherson
2025-04-30 20:30 ` [PATCH v4 3/5] RISC-V: KVM: switch to kvm_trylock/unlock_all_vcpus Maxim Levitsky
2025-04-30 20:30 ` [PATCH v4 4/5] locking/mutex: implement mutex_lock_killable_nest_lock Maxim Levitsky
2025-04-30 20:30 ` [PATCH v4 5/5] x86: KVM: SEV: implement kvm_lock_all_vcpus and use it Maxim Levitsky
2025-05-02 20:57 ` Sean Christopherson
2025-05-03 10:08 ` Peter Zijlstra [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=20250503100820.GF4198@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=mlevitsk@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=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