qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: wei@redhat.com, peter.maydell@linaro.org, drjones@redhat.com,
	libvir-list@redhat.com, armbru@redhat.com,
	mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	qemu-arm@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 0/4] ARM: add query-gic-capabilities SMP command
Date: Wed, 23 Mar 2016 17:17:01 +0800	[thread overview]
Message-ID: <20160323091701.GP28183@pxdev.xzpeter.org> (raw)
In-Reply-To: <1458723243.3546.32.camel@redhat.com>

On Wed, Mar 23, 2016 at 09:54:03AM +0100, Andrea Bolognani wrote:
> On Wed, 2016-03-23 at 13:32 +0800, Peter Xu wrote:
> > v6 changes:
> > - patch 1 (squashed into patch 2)
> >   - explain more about the following in commit message: why we need
> >     this command, and what does the entries mean [Markus]
> >   - explain what GIC is [Eric]
> >   - squash this patch into patch 2 [Eric]
> > - patch 2 (new patch 1)
> >   - fix "does not implement" english error [Eric]
> >   - remove useless headers in target-arm/monitor.c [Markus]
> >   - remove this command from whitelist [Markus, Eric]
> >   - return dict rather than array, with single key points to the
> >     original array results [Markus, Eric]
> > - patch 5 (new patch 4)
> >   - tiny change in implementation to suite the new interface.
> 
> Tested again on two different aarch64 hosts, one with GIC
> v3 support and the other one with GIC v2 only; seems to be
> working just fine.
> 
> Now on to tweak my RFC libvirt patches to cope with the
> interface change :)

Andrea, 

Thank you very much for your quick follow-ups (merely every
time). :-)

Hope that the interface (at least) could suffice this time.

-- peterx

  reply	other threads:[~2016-03-23  9:17 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   ` [Qemu-devel] [Qemu-arm] " Sergey Fedorov
2016-03-24  2:20     ` 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 [this message]
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=20160323091701.GP28183@pxdev.xzpeter.org \
    --to=peterx@redhat.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=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).