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>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: [GIT PULL 00/15] KVM: s390: pv dump and selftest changes
Date: Wed, 1 Jun 2022 17:36:31 +0200 [thread overview]
Message-ID: <20220601153646.6791-1-borntraeger@linux.ibm.com> (raw)
Paolo,
sorry for the late 2nd pull request for 5.19.
It has 3 numbering things that I had to take care of:
api.rst:
4.136 KVM_S390_PV_CPU_COMMAND
8.37 KVM_CAP_S390_PROTECTED_DUMP
kvm.h
define KVM_CAP_S390_PROTECTED_DUMP 217
and then I messed up so patched have been sitting here much longer than
the commit date tells.
Please pull
The following changes since commit 85165781c5d900d97052be1d2723f6929d56768d:
KVM: Do not pin pages tracked by gfn=>pfn caches (2022-05-25 05:23:44 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-5.19-2
for you to fetch changes up to b1edf7f159a6d532757b004a70f31a6425d5043f:
KVM: s390: selftests: Use TAP interface in the reset test (2022-06-01 16:57:15 +0200)
----------------------------------------------------------------
KVM: s390: pvdump and selftest improvements
- add an interface to provide a hypervisor dump for secure guests
- improve selftests to show tests
----------------------------------------------------------------
Janosch Frank (11):
s390/uv: Add SE hdr query information
s390/uv: Add dump fields to query
KVM: s390: pv: Add query interface
KVM: s390: pv: Add dump support definitions
KVM: s390: pv: Add query dump information
KVM: s390: Add configuration dump functionality
KVM: s390: Add CPU dump functionality
KVM: s390: Add KVM_CAP_S390_PROTECTED_DUMP
Documentation: virt: Protected virtual machine dumps
Documentation/virt/kvm/api.rst: Add protvirt dump/info api descriptions
Documentation/virt/kvm/api.rst: Explain rc/rrc delivery
Thomas Huth (4):
KVM: s390: selftests: Use TAP interface in the memop test
KVM: s390: selftests: Use TAP interface in the sync_regs test
KVM: s390: selftests: Use TAP interface in the tprot test
KVM: s390: selftests: Use TAP interface in the reset test
Documentation/virt/kvm/api.rst | 162 ++++++++++++-
Documentation/virt/kvm/s390/index.rst | 1 +
Documentation/virt/kvm/s390/s390-pv-dump.rst | 64 +++++
arch/s390/boot/uv.c | 4 +
arch/s390/include/asm/kvm_host.h | 1 +
arch/s390/include/asm/uv.h | 45 +++-
arch/s390/kernel/uv.c | 53 ++++
arch/s390/kvm/kvm-s390.c | 269 +++++++++++++++++++++
arch/s390/kvm/kvm-s390.h | 5 +
arch/s390/kvm/pv.c | 198 +++++++++++++++
include/uapi/linux/kvm.h | 55 +++++
tools/testing/selftests/kvm/s390x/memop.c | 97 ++++++--
tools/testing/selftests/kvm/s390x/resets.c | 38 ++-
tools/testing/selftests/kvm/s390x/sync_regs_test.c | 87 +++++--
tools/testing/selftests/kvm/s390x/tprot.c | 29 ++-
15 files changed, 1052 insertions(+), 56 deletions(-)
create mode 100644 Documentation/virt/kvm/s390/s390-pv-dump.rst
next reply other threads:[~2022-06-01 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 15:36 Christian Borntraeger [this message]
2022-06-01 15:36 ` [GIT PULL 01/15] s390/uv: Add SE hdr query information Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 02/15] s390/uv: Add dump fields to query Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 03/15] KVM: s390: pv: Add query interface Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 04/15] KVM: s390: pv: Add dump support definitions Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 05/15] KVM: s390: pv: Add query dump information Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 06/15] KVM: s390: Add configuration dump functionality Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 07/15] KVM: s390: Add CPU " Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 08/15] KVM: s390: Add KVM_CAP_S390_PROTECTED_DUMP Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 09/15] Documentation: virt: Protected virtual machine dumps Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 10/15] Documentation/virt/kvm/api.rst: Add protvirt dump/info api descriptions Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 11/15] Documentation/virt/kvm/api.rst: Explain rc/rrc delivery Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 12/15] KVM: s390: selftests: Use TAP interface in the memop test Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 13/15] KVM: s390: selftests: Use TAP interface in the sync_regs test Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 14/15] KVM: s390: selftests: Use TAP interface in the tprot test Christian Borntraeger
2022-06-01 15:36 ` [GIT PULL 15/15] KVM: s390: selftests: Use TAP interface in the reset test Christian Borntraeger
2022-06-07 16:27 ` [GIT PULL 00/15] KVM: s390: pv dump and selftest changes 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=20220601153646.6791-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=pbonzini@redhat.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