From: patchwork-bot+linux-riscv@kernel.org
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: linux-riscv@lists.infradead.org, kvm@vger.kernel.org,
suzuki.poulose@arm.com, jingzhangos@google.com, hpa@zytor.com,
sebott@redhat.com, lishusen2@huawei.com, longman@redhat.com,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
bhelgaas@google.com, bp@alien8.de, anup@brainfault.org,
will@kernel.org, palmer@dabbelt.com, glider@google.com,
kvmarm@lists.linux.dev, keisuke.nishimura@inria.fr,
yuzenghui@huawei.com, peterz@infradead.org,
atishp@atishpatra.org, joey.gouly@arm.com, x86@kernel.org,
maz@kernel.org, seanjc@google.com, andre.przywara@arm.com,
jiangkunkun@huawei.com, rdunlap@infradead.org,
pbonzini@redhat.com, boqun.feng@gmail.com,
catalin.marinas@arm.com, alex@ghiti.fr,
linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
oliver.upton@linux.dev, kvm-riscv@lists.infradead.org,
mingo@redhat.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu
Subject: Re: [PATCH v5 0/6] KVM: lockdep improvements
Date: Tue, 10 Jun 2025 16:28:29 +0000 [thread overview]
Message-ID: <174957290974.2454024.11071746229021073521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250512180407.659015-1-mlevitsk@redhat.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Paolo Bonzini <pbonzini@redhat.com>:
On Mon, 12 May 2025 14:04:01 -0400 you 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().
>
> [...]
Here is the summary with links:
- [v5,1/6] locking/mutex: implement mutex_trylock_nested
https://git.kernel.org/riscv/c/c5b6ababd21a
- [v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock
https://git.kernel.org/riscv/c/fb49f07ba1d9
- [v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus
https://git.kernel.org/riscv/c/e4a454ced74c
- [v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation
https://git.kernel.org/riscv/c/c560bc9286e6
- [v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs
https://git.kernel.org/riscv/c/b586c5d21954
- [v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs
https://git.kernel.org/riscv/c/8f56770d114b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
--
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: linux-riscv@lists.infradead.org, kvm@vger.kernel.org,
suzuki.poulose@arm.com, jingzhangos@google.com, hpa@zytor.com,
sebott@redhat.com, lishusen2@huawei.com, longman@redhat.com,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
bhelgaas@google.com, bp@alien8.de, anup@brainfault.org,
will@kernel.org, palmer@dabbelt.com, glider@google.com,
kvmarm@lists.linux.dev, keisuke.nishimura@inria.fr,
yuzenghui@huawei.com, peterz@infradead.org,
atishp@atishpatra.org, joey.gouly@arm.com, x86@kernel.org,
maz@kernel.org, seanjc@google.com, andre.przywara@arm.com,
jiangkunkun@huawei.com, rdunlap@infradead.org,
pbonzini@redhat.com, boqun.feng@gmail.com,
catalin.marinas@arm.com, alex@ghiti.fr,
linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
oliver.upton@linux.dev, kvm-riscv@lists.infradead.org,
mingo@redhat.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu
Subject: Re: [PATCH v5 0/6] KVM: lockdep improvements
Date: Tue, 10 Jun 2025 16:28:29 +0000 [thread overview]
Message-ID: <174957290974.2454024.11071746229021073521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250512180407.659015-1-mlevitsk@redhat.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Paolo Bonzini <pbonzini@redhat.com>:
On Mon, 12 May 2025 14:04:01 -0400 you 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().
>
> [...]
Here is the summary with links:
- [v5,1/6] locking/mutex: implement mutex_trylock_nested
https://git.kernel.org/riscv/c/c5b6ababd21a
- [v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock
https://git.kernel.org/riscv/c/fb49f07ba1d9
- [v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus
https://git.kernel.org/riscv/c/e4a454ced74c
- [v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation
https://git.kernel.org/riscv/c/c560bc9286e6
- [v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs
https://git.kernel.org/riscv/c/b586c5d21954
- [v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs
https://git.kernel.org/riscv/c/8f56770d114b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: linux-riscv@lists.infradead.org, kvm@vger.kernel.org,
suzuki.poulose@arm.com, jingzhangos@google.com, hpa@zytor.com,
sebott@redhat.com, lishusen2@huawei.com, longman@redhat.com,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
bhelgaas@google.com, bp@alien8.de, anup@brainfault.org,
will@kernel.org, palmer@dabbelt.com, glider@google.com,
kvmarm@lists.linux.dev, keisuke.nishimura@inria.fr,
yuzenghui@huawei.com, peterz@infradead.org,
atishp@atishpatra.org, joey.gouly@arm.com, x86@kernel.org,
maz@kernel.org, seanjc@google.com, andre.przywara@arm.com,
jiangkunkun@huawei.com, rdunlap@infradead.org,
pbonzini@redhat.com, boqun.feng@gmail.com,
catalin.marinas@arm.com, alex@ghiti.fr,
linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
oliver.upton@linux.dev, kvm-riscv@lists.infradead.org,
mingo@redhat.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu
Subject: Re: [PATCH v5 0/6] KVM: lockdep improvements
Date: Tue, 10 Jun 2025 16:28:29 +0000 [thread overview]
Message-ID: <174957290974.2454024.11071746229021073521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250512180407.659015-1-mlevitsk@redhat.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Paolo Bonzini <pbonzini@redhat.com>:
On Mon, 12 May 2025 14:04:01 -0400 you 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().
>
> [...]
Here is the summary with links:
- [v5,1/6] locking/mutex: implement mutex_trylock_nested
https://git.kernel.org/riscv/c/c5b6ababd21a
- [v5,2/6] locking/mutex: implement mutex_lock_killable_nest_lock
https://git.kernel.org/riscv/c/fb49f07ba1d9
- [v5,3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus
https://git.kernel.org/riscv/c/e4a454ced74c
- [v5,4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation
https://git.kernel.org/riscv/c/c560bc9286e6
- [v5,5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs
https://git.kernel.org/riscv/c/b586c5d21954
- [v5,6/6] RISC-V: KVM: use kvm_trylock_all_vcpus when locking all vCPUs
https://git.kernel.org/riscv/c/8f56770d114b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-06-10 19:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 18:04 [PATCH v5 0/6] KVM: lockdep improvements Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` [PATCH v5 1/6] locking/mutex: implement mutex_trylock_nested Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` [PATCH v5 2/6] locking/mutex: implement mutex_lock_killable_nest_lock Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` [PATCH v5 3/6] KVM: add kvm_lock_all_vcpus and kvm_trylock_all_vcpus Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-14 9:33 ` Marc Zyngier
2025-05-14 9:33 ` Marc Zyngier
2025-05-14 9:33 ` Marc Zyngier
2025-05-12 18:04 ` [PATCH v5 4/6] x86: KVM: SVM: use kvm_lock_all_vcpus instead of a custom implementation Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` [PATCH v5 5/6] KVM: arm64: use kvm_trylock_all_vcpus when locking all vCPUs Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-14 9:35 ` Marc Zyngier
2025-05-14 9:35 ` Marc Zyngier
2025-05-14 9:35 ` Marc Zyngier
2025-05-12 18:04 ` [PATCH v5 6/6] RISC-V: KVM: " Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-12 18:04 ` Maxim Levitsky
2025-05-13 11:18 ` Anup Patel
2025-05-13 11:18 ` Anup Patel
2025-05-13 11:18 ` Anup Patel
2025-05-13 11:45 ` [PATCH v5 0/6] KVM: lockdep improvements Peter Zijlstra
2025-05-13 11:45 ` Peter Zijlstra
2025-05-13 11:45 ` Peter Zijlstra
2025-05-27 16:23 ` Paolo Bonzini
2025-06-10 16:28 ` patchwork-bot+linux-riscv [this message]
2025-06-10 16:28 ` patchwork-bot+linux-riscv
2025-06-10 16:28 ` patchwork-bot+linux-riscv
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=174957290974.2454024.11071746229021073521.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.