linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Janosch Frank" <frankja@linux.ibm.com>, <kvm@vger.kernel.org>
Cc: <linux-s390@vger.kernel.org>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Sven Schnelle" <svens@linux.ibm.com>
Subject: Re: [PATCH v2] KVM: S390: Remove sca_lock
Date: Fri, 06 Jun 2025 10:48:17 +0200	[thread overview]
Message-ID: <DAFBJJE5QR8S.1ZL5NPV5EJB6I@linux.ibm.com> (raw)
In-Reply-To: <c024e066-0565-4af3-ae61-bfb995eeea19@linux.ibm.com>

On Fri Jun 6, 2025 at 10:14 AM CEST, Janosch Frank wrote:
> On 6/5/25 6:14 PM, Christoph Schlameuss wrote:
>> Since we are no longer switching from a BSCA to a ESCA we can completely
>> get rid of the sca_lock. The write lock was only taken for that
>> conversion.
>> 
>> After removal of the lock some local code cleanups are possible.
>> 
>> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
>> ---
>> The patch depends on "KVM: s390: Use ESCA instead of BSCA at VM init"
>> 
>> Link: https://lore.kernel.org/r/20250603-rm-bsca-v5-1-f691288ada5c@linux.ibm.com
>
> I'm throwing this into the CI.
>
> If people suggest something, *cough* me for instance *cough*, it doesn't 
> hurt to add a suggested-by tag.

Noted. Will add that if I have to touch this again. Otherwise I assume we can
add this in picking?

      reply	other threads:[~2025-06-06  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 16:14 [PATCH v2] KVM: S390: Remove sca_lock Christoph Schlameuss
2025-06-06  8:14 ` Janosch Frank
2025-06-06  8:48   ` Christoph Schlameuss [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=DAFBJJE5QR8S.1ZL5NPV5EJB6I@linux.ibm.com \
    --to=schlameuss@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.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-s390@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).