From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Subject: [GIT PULL 0/6] KVM: s390: Fix and cleanup for 5.17
Date: Mon, 20 Dec 2021 19:10:58 +0100 [thread overview]
Message-ID: <20211220181104.595009-1-borntraeger@linux.ibm.com> (raw)
Paolo,
the first set of patches for 5.17, mostly cleanups but also one fix. I
will let this go in via next instead of master as we probably have less
non-CI testing during the holidays and it is not security-related.
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-5.17-1
for you to fetch changes up to 812de04661c4daa7ac385c0dfd62594540538034:
KVM: s390: Clarify SIGP orders versus STOP/RESTART (2021-12-17 14:52:47 +0100)
----------------------------------------------------------------
KVM: s390: Fix and cleanup
- fix sigp sense/start/stop/inconsistency
- cleanups
----------------------------------------------------------------
Eric Farman (1):
KVM: s390: Clarify SIGP orders versus STOP/RESTART
Janis Schoetterl-Glausch (4):
KVM: s390: Fix names of skey constants in api documentation
KVM: s390: gaccess: Refactor gpa and length calculation
KVM: s390: gaccess: Refactor access address range check
KVM: s390: gaccess: Cleanup access to guest pages
Janosch Frank (1):
s390: uv: Add offset comments to UV query struct and fix naming
Documentation/virt/kvm/api.rst | 6 +-
arch/s390/include/asm/uv.h | 34 ++++-----
arch/s390/kvm/gaccess.c | 158 ++++++++++++++++++++++++-----------------
arch/s390/kvm/interrupt.c | 7 ++
arch/s390/kvm/kvm-s390.c | 9 ++-
arch/s390/kvm/kvm-s390.h | 1 +
arch/s390/kvm/sigp.c | 28 ++++++++
7 files changed, 155 insertions(+), 88 deletions(-)
next reply other threads:[~2021-12-20 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 18:10 Christian Borntraeger [this message]
2021-12-20 18:10 ` [GIT PULL 1/6] KVM: s390: Fix names of skey constants in api documentation Christian Borntraeger
2021-12-20 18:11 ` [GIT PULL 2/6] KVM: s390: gaccess: Refactor gpa and length calculation Christian Borntraeger
2021-12-20 18:11 ` [GIT PULL 3/6] KVM: s390: gaccess: Refactor access address range check Christian Borntraeger
2021-12-20 18:11 ` [GIT PULL 4/6] KVM: s390: gaccess: Cleanup access to guest pages Christian Borntraeger
2021-12-20 18:11 ` [GIT PULL 5/6] s390: uv: Add offset comments to UV query struct and fix naming Christian Borntraeger
2021-12-20 18:11 ` [GIT PULL 6/6] KVM: s390: Clarify SIGP orders versus STOP/RESTART Christian Borntraeger
2021-12-21 18:41 ` [GIT PULL 0/6] KVM: s390: Fix and cleanup for 5.17 Paolo Bonzini
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=20211220181104.595009-1-borntraeger@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@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 \
--cc=pbonzini@redhat.com \
--cc=scgl@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