From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, drjones@redhat.com,
libvir-list@redhat.com, armbru@redhat.com,
mdroth@linux.vnet.ibm.com, abologna@redhat.com,
qemu-arm@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH v6 4/4] arm: implement query-gic-capabilities
Date: Wed, 23 Mar 2016 15:33:25 +0300 [thread overview]
Message-ID: <56F28D15.5070302@gmail.com> (raw)
In-Reply-To: <1458711153-15988-5-git-send-email-peterx@redhat.com>
On 23/03/16 08:32, Peter Xu wrote:
> diff --git a/target-arm/monitor.c b/target-arm/monitor.c
> index 254a9c9..4a2db59 100644
> --- a/target-arm/monitor.c
> +++ b/target-arm/monitor.c
> @@ -21,8 +21,66 @@
(snip)
> GICCapabilityResult *qmp_query_gic_capabilities(Error **errp)
> {
> - return NULL;
> + GICCapabilityResult *result = g_new0(GICCapabilityResult, 1);
> + GICCapabilityList *head = NULL;
> + GICCapability *v2 = gic_cap_new(2), *v3 = gic_cap_new(3);
> +
> + v2->emulated = true;
> + /* FIXME: we'd change to true after we get emulated GICv3. */
Maybewe'd better use'NOTE:' or 'TODO:' instead of 'FIXME:'?
> + v3->emulated = false;
> +
> +#ifdef CONFIG_KVM
> + {
> + int fdarray[3];
> +
> + if (!kvm_arm_create_scratch_host_vcpu(NULL, fdarray, NULL)) {
> + goto out;
> + }
> +
> + /* Test KVM GICv2 */
> + if (kvm_support_device(fdarray[1], KVM_DEV_TYPE_ARM_VGIC_V2)) {
> + v2->kernel = true;
> + }
> +
> + /* Test KVM GICv3 */
> + if (kvm_support_device(fdarray[1], KVM_DEV_TYPE_ARM_VGIC_V3)) {
> + v3->kernel = true;
> + }
> +
> + kvm_arm_destroy_scratch_host_vcpu(fdarray);
> +out:
> + ;
> + }
> +#endif
Probably, it would be neater to put KVM part into a separate static
inline function.
Kind regards,
Sergey
> +
> + head = gic_cap_list_add(head, v2);
> + head = gic_cap_list_add(head, v3);
> +
> + result->capabilities = head;
> +
> + return result;
> }
next prev parent reply other threads:[~2016-03-23 12:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 5:32 [Qemu-devel] [PATCH v6 0/4] ARM: add query-gic-capabilities SMP command Peter Xu
2016-03-23 5:32 ` [Qemu-devel] [PATCH v6 1/4] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-23 5:32 ` [Qemu-devel] [PATCH v6 2/4] arm: enhance kvm_arm_create_scratch_host_vcpu Peter Xu
2016-03-23 12:24 ` [Qemu-devel] [Qemu-arm] " Sergey Fedorov
2016-03-23 14:53 ` Peter Xu
2016-03-23 5:32 ` [Qemu-devel] [PATCH v6 3/4] kvm: add kvm_support_device() helper function Peter Xu
2016-03-23 12:28 ` Sergey Fedorov
2016-03-23 14:56 ` Peter Xu
2016-03-23 15:03 ` Sergey Fedorov
2016-03-24 1:59 ` Peter Xu
2016-03-23 5:32 ` [Qemu-devel] [PATCH v6 4/4] arm: implement query-gic-capabilities Peter Xu
2016-03-23 12:33 ` Sergey Fedorov [this message]
2016-03-24 2:20 ` [Qemu-devel] [Qemu-arm] " Peter Xu
2016-03-23 5:57 ` [Qemu-devel] [PATCH v6 0/4] ARM: add query-gic-capabilities SMP command Peter Xu
2016-03-23 8:54 ` Andrea Bolognani
2016-03-23 9:17 ` Peter Xu
2016-03-23 10:32 ` Christoffer Dall
2016-03-23 11:34 ` 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=56F28D15.5070302@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=libvir-list@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 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).