From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Claudio Imbrenda" <imbrenda@linux.ibm.com>,
<linux-kernel@vger.kernel.org>
Cc: <kvm@vger.kernel.org>, <linux-s390@vger.kernel.org>,
<frankja@linux.ibm.com>, <borntraeger@de.ibm.com>,
<seiden@linux.ibm.com>, <nsg@linux.ibm.com>, <nrb@linux.ibm.com>,
<david@redhat.com>, <hca@linux.ibm.com>, <agordeev@linux.ibm.com>,
<svens@linux.ibm.com>, <gor@linux.ibm.com>
Subject: Re: [PATCH v3 2/4] KVM: s390: remove unneeded srcu lock
Date: Thu, 22 May 2025 15:44:14 +0200 [thread overview]
Message-ID: <DA2QFYNT6G6B.3JVSDMJGGBL7N@linux.ibm.com> (raw)
In-Reply-To: <20250522132259.167708-3-imbrenda@linux.ibm.com>
On Thu May 22, 2025 at 3:22 PM CEST, Claudio Imbrenda wrote:
> All paths leading to handle_essa() already hold the kvm->srcu.
> Remove unneeded srcu locking from handle_essa().
> Add lockdep assertion to make sure we will always be holding kvm->srcu
> when entering handle_essa().
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Reviewed-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Reviewed-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
> arch/s390/kvm/priv.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/arch/s390/kvm/priv.c b/arch/s390/kvm/priv.c
> index 1a49b89706f8..9253c70897a8 100644
> --- a/arch/s390/kvm/priv.c
> +++ b/arch/s390/kvm/priv.c
> @@ -1248,6 +1248,8 @@ static inline int __do_essa(struct kvm_vcpu *vcpu, const int orc)
>
> static int handle_essa(struct kvm_vcpu *vcpu)
> {
> + lockdep_assert_held(&vcpu->kvm->srcu);
> +
> /* entries expected to be 1FF */
> int entries = (vcpu->arch.sie_block->cbrlo & ~PAGE_MASK) >> 3;
> unsigned long *cbrlo;
> @@ -1297,12 +1299,8 @@ static int handle_essa(struct kvm_vcpu *vcpu)
> /* Retry the ESSA instruction */
> kvm_s390_retry_instr(vcpu);
> } else {
> - int srcu_idx;
> -
> mmap_read_lock(vcpu->kvm->mm);
> - srcu_idx = srcu_read_lock(&vcpu->kvm->srcu);
> i = __do_essa(vcpu, orc);
> - srcu_read_unlock(&vcpu->kvm->srcu, srcu_idx);
> mmap_read_unlock(vcpu->kvm->mm);
> if (i < 0)
> return i;
next prev parent reply other threads:[~2025-05-22 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 13:22 [PATCH v3 0/4] KVM: s390: some cleanup and small fixes Claudio Imbrenda
2025-05-22 13:22 ` [PATCH v3 1/4] s390: remove unneeded includes Claudio Imbrenda
2025-05-22 13:50 ` Steffen Eiden
2025-05-22 13:22 ` [PATCH v3 2/4] KVM: s390: remove unneeded srcu lock Claudio Imbrenda
2025-05-22 13:44 ` Christoph Schlameuss [this message]
2025-05-22 13:57 ` Steffen Eiden
2025-05-22 13:22 ` [PATCH v3 3/4] KVM: s390: refactor and split some gmap helpers Claudio Imbrenda
2025-05-22 14:49 ` Steffen Eiden
2025-05-22 18:04 ` Christoph Schlameuss
2025-05-23 1:03 ` kernel test robot
2025-05-23 3:48 ` kernel test robot
2025-05-22 13:22 ` [PATCH v3 4/4] KVM: s390: simplify and move pv code Claudio Imbrenda
2025-05-22 14:57 ` Steffen Eiden
2025-05-22 18:40 ` Christoph Schlameuss
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=DA2QFYNT6G6B.3JVSDMJGGBL7N@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=seiden@linux.ibm.com \
--cc=svens@linux.ibm.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