public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: KVM <kvm@vger.kernel.org>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Thomas Huth <thuth@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Subject: [PATCH 0/2] s390/gmap/pgtable improve handling of keyed KVM guests
Date: Mon, 30 May 2022 11:27:04 +0200	[thread overview]
Message-ID: <20220530092706.11637-1-borntraeger@linux.ibm.com> (raw)

These two patches try to address stalls/timeouts that we have seen when
switching many guests to enable storage keys.

Christian Borntraeger (2):
  s390/gmap: voluntarily schedule during key setting
  s390/pgtable: use non-quiescing sske for KVM switch to keyed

 arch/s390/mm/gmap.c    | 14 ++++++++++++++
 arch/s390/mm/pgtable.c |  2 +-
 2 files changed, 15 insertions(+), 1 deletion(-)

-- 
2.35.1


             reply	other threads:[~2022-05-30  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  9:27 Christian Borntraeger [this message]
2022-05-30  9:27 ` [PATCH 1/2] s390/gmap: voluntarily schedule during key setting Christian Borntraeger
2022-05-30  9:56   ` Claudio Imbrenda
2022-05-31  7:23   ` Alexander Gordeev
2022-05-30  9:27 ` [PATCH 2/2] s390/pgtable: use non-quiescing sske for KVM switch to keyed Christian Borntraeger
2022-05-30  9:56   ` Claudio Imbrenda
2022-05-31  8:28 ` [PATCH 0/2] s390/gmap/pgtable improve handling of keyed KVM guests Christian Borntraeger

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=20220530092706.11637-1-borntraeger@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=agordeev@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=scgl@linux.ibm.com \
    --cc=thuth@redhat.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