qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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>,
	Markus Armbruster <armbru@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] ARM: add query-gic-capabilities SMP command
Date: Wed, 16 Mar 2016 11:42:26 +0100	[thread overview]
Message-ID: <1458124946.8641.27.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA9QnbcUZyY_=Moi3P+wS27d4Q16e62jKOvNMhO2L72S-Q@mail.gmail.com>

On Wed, 2016-03-16 at 10:32 +0000, Peter Maydell wrote:
> On 8 March 2016 at 07:36, Peter Xu <peterx@redhat.com> wrote:
> > 
> > v4 changes:
> > - all: rename query-gic-capability to query-gic-capabilities [Andrea]
> > - patch 3: rename helper function to kvm_support_device, make it
> >   inline and lighter. [Drew]
> > 
> > v3 changes:
> > - patch 2: remove func declaration, add qmp header [Drew]
> > - patch 3: being able to detect KVM GIC capabilities even without
> >   kvm enabled [Andrea]: this is a little bit hacky, need some more
> >   review on this.
> > 
> > v2 changes:
> > - result layout change: use array and dict for the capability bits
> >   rather than a single array of strings [Andrea/Markus]
> > - spelling out what GIC is in doc [Eric]
> > 
> > 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.
> 
> Hi. I've made some code review comments on the specifics of the
> implementation, but really what I'd like to see is:
>  * an ack from the libvirt folks that this API meets their
>    requirements

I have a working implementation of the libvirt part, but I need
to polish it up before it can be posted on the list; then other
libvirt folks will be able to provide feedback.

Cheers.

-- 
Andrea Bolognani
Software Engineer - Virtualization Team

      reply	other threads:[~2016-03-16 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  7:36 [Qemu-devel] [PATCH v4 0/3] ARM: add query-gic-capabilities SMP command Peter Xu
2016-03-08  7:36 ` [Qemu-devel] [PATCH v4 1/3] arm: qmp: add GICCapability struct Peter Xu
2016-03-08  7:36 ` [Qemu-devel] [PATCH v4 2/3] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-16 10:24   ` Peter Maydell
2016-03-17  4:09     ` Peter Xu
2016-03-17  8:50       ` Peter Maydell
2016-03-17  9:09         ` Peter Xu
2016-03-08  7:36 ` [Qemu-devel] [PATCH v4 3/3] arm: implement query-gic-capabilities Peter Xu
2016-03-16 10:30   ` Peter Maydell
2016-03-17  9:40     ` Peter Xu
2016-03-16 10:32 ` [Qemu-devel] [PATCH v4 0/3] ARM: add query-gic-capabilities SMP command Peter Maydell
2016-03-16 10:42   ` Andrea Bolognani [this message]

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=1458124946.8641.27.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=armbru@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 \
    --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).