All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	linux-s390@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>
Subject: [PATCH 0/2] KVM: s390: Fix V!=R bug in STFLE shadowing
Date: Tue, 19 Mar 2024 17:44:18 +0100	[thread overview]
Message-ID: <20240319164420.4053380-1-nsg@linux.ibm.com> (raw)

The address of the facility control block is a physical address,
and therefore requires conversion from virtual (patch 2).

Also send unrelated patch 1 which was previously sent as part of
"KVM: s390: Fix minor bugs in STFLE shadowing" but deferred.

Nina Schoetterl-Glausch (2):
  KVM: s390: Minor refactor of base/ext facility lists
  KVM: s390: vsie: Use virt_to_phys for facility control block

 arch/s390/kvm/kvm-s390.c | 44 +++++++++++++++++-----------------------
 arch/s390/kvm/vsie.c     |  3 ++-
 2 files changed, 21 insertions(+), 26 deletions(-)


base-commit: e8f897f4afef0031fe618a8e94127a0934896aba
-- 
2.40.1


             reply	other threads:[~2024-03-19 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 16:44 Nina Schoetterl-Glausch [this message]
2024-03-19 16:44 ` [PATCH RESEND 1/2] KVM: s390: Minor refactor of base/ext facility lists Nina Schoetterl-Glausch
2024-03-19 16:44 ` [PATCH 2/2] KVM: s390: vsie: Use virt_to_phys for facility control block Nina Schoetterl-Glausch
2024-03-20 11:35   ` David Hildenbrand

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=20240319164420.4053380-1-nsg@linux.ibm.com \
    --to=nsg@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-kernel@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 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.