From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, borntraeger@linux.ibm.com,
imbrenda@linux.ibm.com
Subject: [PATCH v6 08/11] kvm: s390: Add KVM_CAP_S390_PROTECTED_DUMP
Date: Tue, 17 May 2022 16:36:26 +0000 [thread overview]
Message-ID: <20220517163629.3443-9-frankja@linux.ibm.com> (raw)
In-Reply-To: <20220517163629.3443-1-frankja@linux.ibm.com>
The capability indicates dump support for protected VMs.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
---
arch/s390/kvm/kvm-s390.c | 20 ++++++++++++++++++++
include/uapi/linux/kvm.h | 1 +
2 files changed, 21 insertions(+)
diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
index 1938756d4a32..99ce1aced86b 100644
--- a/arch/s390/kvm/kvm-s390.c
+++ b/arch/s390/kvm/kvm-s390.c
@@ -606,6 +606,26 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
case KVM_CAP_S390_PROTECTED:
r = is_prot_virt_host();
break;
+ case KVM_CAP_S390_PROTECTED_DUMP: {
+ u64 pv_cmds_dump[] = {
+ BIT_UVC_CMD_DUMP_INIT,
+ BIT_UVC_CMD_DUMP_CONFIG_STOR_STATE,
+ BIT_UVC_CMD_DUMP_CPU,
+ BIT_UVC_CMD_DUMP_COMPLETE,
+ };
+ int i;
+
+ r = is_prot_virt_host();
+
+ for (i = 0; i < ARRAY_SIZE(pv_cmds_dump); i++) {
+ if (!test_bit_inv(pv_cmds_dump[i],
+ (unsigned long *)&uv_info.inst_calls_list)) {
+ r = 0;
+ break;
+ }
+ }
+ break;
+ }
default:
r = 0;
}
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index 204b06e3a50b..108bc7b7a71b 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1144,6 +1144,7 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_S390_MEM_OP_EXTENSION 211
#define KVM_CAP_PMU_CAPABILITY 212
#define KVM_CAP_DISABLE_QUIRKS2 213
+#define KVM_CAP_S390_PROTECTED_DUMP 214
#ifdef KVM_CAP_IRQ_ROUTING
--
2.34.1
next prev parent reply other threads:[~2022-05-17 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 16:36 [PATCH v6 00/11] kvm: s390: Add PV dump support Janosch Frank
2022-05-17 16:36 ` [PATCH v6 01/11] s390x: Add SE hdr query information Janosch Frank
2022-05-17 16:36 ` [PATCH v6 02/11] s390: uv: Add dump fields to query Janosch Frank
2022-05-17 16:36 ` [PATCH v6 03/11] KVM: s390: pv: Add query interface Janosch Frank
2022-05-17 16:36 ` [PATCH v6 04/11] KVM: s390: pv: Add dump support definitions Janosch Frank
2022-05-17 16:36 ` [PATCH v6 05/11] KVM: s390: pv: Add query dump information Janosch Frank
2022-05-17 16:36 ` [PATCH v6 06/11] kvm: s390: Add configuration dump functionality Janosch Frank
2022-05-17 16:54 ` Claudio Imbrenda
2022-05-17 16:36 ` [PATCH v6 07/11] kvm: s390: Add CPU " Janosch Frank
2022-05-17 16:48 ` Claudio Imbrenda
2022-05-17 16:36 ` Janosch Frank [this message]
2022-05-17 16:48 ` [PATCH v6 08/11] kvm: s390: Add KVM_CAP_S390_PROTECTED_DUMP Claudio Imbrenda
2022-05-17 16:36 ` [PATCH v6 09/11] Documentation: virt: Protected virtual machine dumps Janosch Frank
2022-05-17 16:36 ` [PATCH v6 10/11] Documentation/virt/kvm/api.rst: Add protvirt dump/info api descriptions Janosch Frank
2022-05-17 16:47 ` Claudio Imbrenda
2022-05-17 16:36 ` [PATCH v6 11/11] Documentation/virt/kvm/api.rst: Explain rc/rrc delivery Janosch Frank
2022-05-17 16:47 ` Claudio Imbrenda
2022-05-30 13:10 ` [PATCH v6 00/11] kvm: s390: Add PV dump support 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=20220517163629.3443-9-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@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