From: Andrea Bolognani <abologna@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Peter Xu <peterx@redhat.com>
Cc: Wei Huang <wei@redhat.com>, Andrew Jones <drjones@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Libvirt <libvir-list@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>,
Sergey Fedorov <serge.fdrv@gmail.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v7 0/4] ARM: add query-gic-capabilities QMP command
Date: Wed, 30 Mar 2016 13:20:21 +0200 [thread overview]
Message-ID: <1459336821.4699.13.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Y=nXpaNmOUNPzsFBhSZES9SD2k+u3XhVhzABOr9qGrw@mail.gmail.com>
On Tue, 2016-03-29 at 21:10 +0100, Peter Maydell wrote:
> On 24 March 2016 at 02:55, Peter Xu <peterx@redhat.com> wrote:
> >
> > This patch is to add ARM-specific command "query-gic-capability".
> >
> > The new command can report which kind of GIC device the host/QEMU
> > support. The returned result is in the form of array.
> >
> > Sample command and output:
> >
> > {"execute": "query-gic-capability"}
> > {"return": [{"emulated": false, "version": 3, "kernel": false},
> > {"emulated": true, "version": 2, "kernel": true}]}
>
> I really strongly want this in 2.6 but we are very very nearly
> out of time. Eric or Markus, could I trouble one of you to
> provide an ack for this series for the QMP protocol aspects
> sometime before end of Wednesday, please?
>
> I also don't think I've seen an indication from the libvirt
> folks that this is definitely the API they want; did I miss it?
Yes, this works nicely for libvirt; in fact, I've already
posted an RFC implementation[1] to the list last week.
Cheers.
[1] https://www.redhat.com/archives/libvir-list/2016-March/msg00956.html
--
Andrea Bolognani
Software Engineer - Virtualization Team
next prev parent reply other threads:[~2016-03-30 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 2:55 [Qemu-devel] [PATCH v7 0/4] ARM: add query-gic-capabilities QMP command Peter Xu
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 1/4] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-30 1:50 ` Eric Blake
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 2/4] arm: enhance kvm_arm_create_scratch_host_vcpu Peter Xu
2016-03-24 9:13 ` Sergey Fedorov
2016-03-29 20:04 ` Peter Maydell
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 3/4] kvm: add kvm_device_supported() helper function Peter Xu
2016-03-24 9:14 ` Sergey Fedorov
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 4/4] arm: implement query-gic-capabilities Peter Xu
2016-03-24 9:16 ` Sergey Fedorov
2016-03-29 20:10 ` [Qemu-devel] [PATCH v7 0/4] ARM: add query-gic-capabilities QMP command Peter Maydell
2016-03-30 11:20 ` Andrea Bolognani [this message]
2016-03-30 14:53 ` Peter Maydell
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=1459336821.4699.13.camel@redhat.com \
--to=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=christoffer.dall@linaro.org \
--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 \
--cc=serge.fdrv@gmail.com \
--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).