From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: wei@redhat.com, peter.maydell@linaro.org, drjones@redhat.com,
mdroth@linux.vnet.ibm.com, armbru@redhat.com, peterx@redhat.com,
abologna@redhat.com, qemu-arm@nongnu.org
Subject: [Qemu-devel] [PATCH v5 1/5] arm: qmp: add GICCapability struct
Date: Fri, 18 Mar 2016 11:27:30 +0800 [thread overview]
Message-ID: <1458271654-23706-2-git-send-email-peterx@redhat.com> (raw)
In-Reply-To: <1458271654-23706-1-git-send-email-peterx@redhat.com>
Define new struct to describe whether we support specific GIC version.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
qapi-schema.json | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/qapi-schema.json b/qapi-schema.json
index f253a37..da9671a 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -4134,3 +4134,25 @@
##
{ 'enum': 'ReplayMode',
'data': [ 'none', 'record', 'play' ] }
+
+##
+# @GICCapability:
+#
+# This struct describes capability for a specific GIC version. These
+# bits are not only decided by QEMU/KVM software version, but also
+# decided by the hardware that the program is running upon.
+#
+# @version: version of GIC to be described.
+#
+# @emulated: whether current QEMU/hardware supports emulated GIC
+# device in user space.
+#
+# @kernel: whether current QEMU/hardware supports hardware
+# accelerated GIC device in kernel.
+#
+# Since: 2.6
+##
+{ 'struct': 'GICCapability',
+ 'data': { 'version': 'int',
+ 'emulated': 'bool',
+ 'kernel': 'bool' } }
--
2.4.3
next prev parent reply other threads:[~2016-03-18 3:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 3:27 [Qemu-devel] [PATCH v5 0/5] ARM: add query-gic-capabilities SMP command Peter Xu
2016-03-18 3:27 ` Peter Xu [this message]
2016-03-22 18:29 ` [Qemu-devel] [PATCH v5 1/5] arm: qmp: add GICCapability struct Markus Armbruster
2016-03-22 18:41 ` Markus Armbruster
2016-03-23 2:58 ` Peter Xu
2016-03-23 9:33 ` Markus Armbruster
2016-03-23 11:48 ` Peter Xu
2016-03-23 12:21 ` Markus Armbruster
2016-03-23 14:25 ` Peter Xu
2016-03-23 15:17 ` Markus Armbruster
2016-03-24 2:27 ` Peter Xu
2016-03-22 18:32 ` Eric Blake
2016-03-23 3:09 ` Peter Xu
2016-03-23 9:44 ` Markus Armbruster
2016-03-23 11:56 ` Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 2/5] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-22 18:28 ` Markus Armbruster
2016-03-23 4:14 ` Peter Xu
2016-03-23 9:52 ` Markus Armbruster
2016-03-23 12:04 ` Peter Xu
2016-03-23 14:06 ` Markus Armbruster
2016-03-23 14:31 ` Eric Blake
2016-03-22 18:42 ` Eric Blake
2016-03-22 19:09 ` Markus Armbruster
2016-03-23 4:07 ` Peter Xu
2016-03-23 9:54 ` Markus Armbruster
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 3/5] arm: enhance kvm_arm_create_scratch_host_vcpu Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 4/5] kvm: add kvm_support_device() helper function Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 5/5] arm: implement query-gic-capabilities Peter Xu
2016-03-21 15:56 ` [Qemu-devel] [PATCH v5 0/5] ARM: add query-gic-capabilities SMP command Andrea Bolognani
2016-03-22 2:23 ` Peter Xu
2016-03-22 14:20 ` Markus Armbruster
2016-03-23 5:19 ` Peter Xu
2016-03-22 14:49 ` Peter Maydell
2016-03-23 5:43 ` Peter Xu
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=1458271654-23706-2-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@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).