From: Eric Farman <farman@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Huth <thuth@redhat.com>
Cc: Eric Farman <farman@linux.ibm.com>,
qemu-s390x@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>
Subject: [RFC PATCH v2 1/2] Temporary linux-headers update
Date: Tue, 2 Nov 2021 21:11:21 +0100 [thread overview]
Message-ID: <20211102201122.3188108-2-farman@linux.ibm.com> (raw)
In-Reply-To: <20211102201122.3188108-1-farman@linux.ibm.com>
This should be replaced with ./scripts/update-linux-headers.sh
But this is enough for the RFC.
Signed-off-by: Eric Farman <farman@linux.ibm.com>
---
| 4 ++++
1 file changed, 4 insertions(+)
--git a/linux-headers/linux/kvm.h b/linux-headers/linux/kvm.h
index bcaf66cc4d..b70b3b3148 100644
--- a/linux-headers/linux/kvm.h
+++ b/linux-headers/linux/kvm.h
@@ -1112,6 +1112,7 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_BINARY_STATS_FD 203
#define KVM_CAP_EXIT_ON_EMULATION_FAILURE 204
#define KVM_CAP_ARM_MTE 205
+#define KVM_CAP_S390_USER_SIGP_BUSY 206
#ifdef KVM_CAP_IRQ_ROUTING
@@ -2004,4 +2005,7 @@ struct kvm_stats_desc {
#define KVM_GET_STATS_FD _IO(KVMIO, 0xce)
+/* Available with KVM_CAP_S390_USER_SIGP_BUSY */
+#define KVM_S390_VCPU_RESET_SIGP_BUSY _IO(KVMIO, 0xcf)
+
#endif /* __LINUX_KVM_H */
--
2.25.1
next prev parent reply other threads:[~2021-11-02 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 20:11 [RFC PATCH v2 0/2] s390x: Improvements to SIGP handling [QEMU] Eric Farman
2021-11-02 20:11 ` Eric Farman [this message]
2021-11-02 20:11 ` [RFC PATCH v2 2/2] s390x: Implement the USER_SIGP_BUSY capability Eric Farman
2021-11-04 8:23 ` David Hildenbrand
2021-11-04 14:55 ` Eric Farman
2021-11-04 15:08 ` 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=20211102201122.3188108-2-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).