From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: peter.maydell@linaro.org, drjones@redhat.com,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
abologna@redhat.com, qemu-arm@nongnu.org
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH v5 1/5] arm: qmp: add GICCapability struct
Date: Tue, 22 Mar 2016 19:41:17 +0100 [thread overview]
Message-ID: <87vb4eicdu.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <87zitqjrhj.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Tue, 22 Mar 2016 19:29:44 +0100")
Markus Armbruster <armbru@redhat.com> writes:
> Peter Xu <peterx@redhat.com> writes:
>
>> 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' } }
>
> Are all four combinations of (emulated, kernel) possible?
Moreover, what do the combinations mean from a practical point of view?
What would a management application do with the information?
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: wei@redhat.com, peter.maydell@linaro.org, drjones@redhat.com,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
abologna@redhat.com, qemu-arm@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 1/5] arm: qmp: add GICCapability struct
Date: Tue, 22 Mar 2016 19:41:17 +0100 [thread overview]
Message-ID: <87vb4eicdu.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <87zitqjrhj.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Tue, 22 Mar 2016 19:29:44 +0100")
Markus Armbruster <armbru@redhat.com> writes:
> Peter Xu <peterx@redhat.com> writes:
>
>> 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' } }
>
> Are all four combinations of (emulated, kernel) possible?
Moreover, what do the combinations mean from a practical point of view?
What would a management application do with the information?
next prev parent reply other threads:[~2016-03-22 18:41 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 3:27 [Qemu-arm] [PATCH v5 0/5] ARM: add query-gic-capabilities SMP command Peter Xu
2016-03-18 3:27 ` [Qemu-devel] " Peter Xu
2016-03-18 3:27 ` [Qemu-arm] [PATCH v5 1/5] arm: qmp: add GICCapability struct Peter Xu
2016-03-18 3:27 ` [Qemu-devel] " Peter Xu
2016-03-22 18:29 ` [Qemu-arm] " Markus Armbruster
2016-03-22 18:29 ` Markus Armbruster
2016-03-22 18:41 ` Markus Armbruster [this message]
2016-03-22 18:41 ` Markus Armbruster
2016-03-23 2:58 ` [Qemu-arm] " Peter Xu
2016-03-23 2:58 ` Peter Xu
2016-03-23 9:33 ` [Qemu-arm] " Markus Armbruster
2016-03-23 9:33 ` Markus Armbruster
2016-03-23 11:48 ` [Qemu-arm] " Peter Xu
2016-03-23 11:48 ` Peter Xu
2016-03-23 12:21 ` [Qemu-arm] " Markus Armbruster
2016-03-23 12:21 ` Markus Armbruster
2016-03-23 14:25 ` [Qemu-arm] " Peter Xu
2016-03-23 14:25 ` Peter Xu
2016-03-23 15:17 ` [Qemu-arm] " Markus Armbruster
2016-03-23 15:17 ` Markus Armbruster
2016-03-24 2:27 ` [Qemu-arm] " Peter Xu
2016-03-24 2:27 ` Peter Xu
2016-03-22 18:32 ` [Qemu-arm] " Eric Blake
2016-03-22 18:32 ` [Qemu-devel] " Eric Blake
2016-03-23 3:09 ` [Qemu-arm] " Peter Xu
2016-03-23 3:09 ` [Qemu-devel] " Peter Xu
2016-03-23 9:44 ` [Qemu-arm] " Markus Armbruster
2016-03-23 9:44 ` Markus Armbruster
2016-03-23 11:56 ` [Qemu-arm] " Peter Xu
2016-03-23 11:56 ` Peter Xu
2016-03-18 3:27 ` [Qemu-arm] [PATCH v5 2/5] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-18 3:27 ` [Qemu-devel] " Peter Xu
2016-03-22 18:28 ` [Qemu-arm] " Markus Armbruster
2016-03-22 18:28 ` Markus Armbruster
2016-03-23 4:14 ` [Qemu-arm] " Peter Xu
2016-03-23 4:14 ` Peter Xu
2016-03-23 9:52 ` [Qemu-arm] " Markus Armbruster
2016-03-23 9:52 ` Markus Armbruster
2016-03-23 12:04 ` [Qemu-arm] " Peter Xu
2016-03-23 12:04 ` Peter Xu
2016-03-23 14:06 ` [Qemu-arm] " Markus Armbruster
2016-03-23 14:06 ` Markus Armbruster
2016-03-23 14:31 ` [Qemu-arm] " Eric Blake
2016-03-23 14:31 ` Eric Blake
2016-03-22 18:42 ` [Qemu-arm] " Eric Blake
2016-03-22 18:42 ` [Qemu-devel] " Eric Blake
2016-03-22 19:09 ` [Qemu-arm] " Markus Armbruster
2016-03-22 19:09 ` Markus Armbruster
2016-03-23 4:07 ` [Qemu-arm] " Peter Xu
2016-03-23 4:07 ` [Qemu-devel] " Peter Xu
2016-03-23 9:54 ` [Qemu-arm] " Markus Armbruster
2016-03-23 9:54 ` Markus Armbruster
2016-03-18 3:27 ` [Qemu-arm] [PATCH v5 3/5] arm: enhance kvm_arm_create_scratch_host_vcpu Peter Xu
2016-03-18 3:27 ` [Qemu-devel] " Peter Xu
2016-03-18 3:27 ` [Qemu-arm] [PATCH v5 4/5] kvm: add kvm_support_device() helper function Peter Xu
2016-03-18 3:27 ` [Qemu-devel] " Peter Xu
2016-03-18 3:27 ` [Qemu-arm] [PATCH v5 5/5] arm: implement query-gic-capabilities Peter Xu
2016-03-18 3:27 ` [Qemu-devel] " Peter Xu
2016-03-21 15:56 ` [Qemu-arm] [PATCH v5 0/5] ARM: add query-gic-capabilities SMP command Andrea Bolognani
2016-03-21 15:56 ` [Qemu-devel] " Andrea Bolognani
2016-03-22 2:23 ` [Qemu-arm] " Peter Xu
2016-03-22 2:23 ` [Qemu-devel] " Peter Xu
2016-03-22 14:20 ` [Qemu-arm] " Markus Armbruster
2016-03-22 14:20 ` Markus Armbruster
2016-03-23 5:19 ` [Qemu-arm] " Peter Xu
2016-03-23 5:19 ` Peter Xu
2016-03-22 14:49 ` Peter Maydell
2016-03-23 5:43 ` [Qemu-arm] " Peter Xu
2016-03-23 5:43 ` [Qemu-devel] " 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=87vb4eicdu.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.