From: Nico Boehr <nrb@linux.ibm.com>
To: borntraeger@linux.ibm.com, frankja@linux.ibm.com, imbrenda@linux.ibm.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com
Subject: [v1 0/5] KVM: s390: Fix virtual-real address confusions
Date: Thu, 20 Oct 2022 16:31:54 +0200 [thread overview]
Message-ID: <20221020143159.294605-1-nrb@linux.ibm.com> (raw)
This series fixes several virtual-real address confusions in the basic
KVM infrastructure for s390.
Since physical addresses are currently equal to virtual addresses in
kernel space, the address confusions do not represent issues at the
moment.
IO-related fixes are going to follow in further series.
Nico Boehr (5):
s390/mm: gmap: sort out physical vs virtual pointers usage
s390/entry: sort out physical vs virtual pointers usage in sie64a
KVM: s390: sort out physical vs virtual pointers usage
KVM: s390: sida: sort out physical vs virtual pointers usage
KVM: s390: pv: sort out physical vs virtual pointers usage
arch/s390/include/asm/kvm_host.h | 12 ++-
arch/s390/include/asm/stacktrace.h | 1 +
arch/s390/kernel/asm-offsets.c | 1 +
arch/s390/kernel/entry.S | 26 ++---
arch/s390/kvm/intercept.c | 9 +-
arch/s390/kvm/kvm-s390.c | 53 ++++++-----
arch/s390/kvm/kvm-s390.h | 5 +-
arch/s390/kvm/priv.c | 3 +-
arch/s390/kvm/pv.c | 17 ++--
arch/s390/mm/gmap.c | 147 +++++++++++++++--------------
10 files changed, 150 insertions(+), 124 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-20 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 14:31 Nico Boehr [this message]
2022-10-20 14:31 ` [v1 1/5] s390/mm: gmap: sort out physical vs virtual pointers usage Nico Boehr
2022-10-20 14:31 ` [v1 2/5] s390/entry: sort out physical vs virtual pointers usage in sie64a Nico Boehr
2022-10-20 14:31 ` [v1 3/5] KVM: s390: sort out physical vs virtual pointers usage Nico Boehr
2022-10-20 14:31 ` [v1 4/5] KVM: s390: sida: " Nico Boehr
2022-10-20 14:31 ` [v1 5/5] KVM: s390: pv: " Nico Boehr
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=20221020143159.294605-1-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.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 \
/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