From: Peter Xu <peterx@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: wei@redhat.com, peter.maydell@linaro.org, drjones@redhat.com,
Libvirt Mailing List <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 v5 0/5] ARM: add query-gic-capabilities SMP command
Date: Tue, 22 Mar 2016 10:23:27 +0800 [thread overview]
Message-ID: <20160322022327.GA26867@pxdev.xzpeter.org> (raw)
In-Reply-To: <1458575767.3546.11.camel@redhat.com>
On Mon, Mar 21, 2016 at 04:56:07PM +0100, Andrea Bolognani wrote:
> On Fri, 2016-03-18 at 11:27 +0800, Peter Xu wrote:
> > v5 changes:
> > - patch 2: moved to target-arm/monitor.c (from target-arm/machine.c)
> > [Peter]
> > - patch 3: splitted into three patches: [all from Peter's comments]
> > - patch 3 (new): leverage kvm_arm_create_scratch_host_vcpu(), tiny
> > enhancement of old one to suite our need
> > - patch 4: introduce kvm_support_device() in kvm-all.c
> > - patch 5: do the implementation.
>
> Tested on two separate aarch64 hosts, seems to work fine.
Thanks Andrea!
Sorry I forgot to CC libvir-list. To avoid duplication, not
re-sending but CCing in this reply. If anyone interested, please
review in the following link:
https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg04465.html
(which points to exactly current thread.)
Sorry for the inconvenience!
-- peterx
next prev parent reply other threads:[~2016-03-22 2:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 3:27 [Qemu-devel] [PATCH v5 0/5] ARM: add query-gic-capabilities SMP command Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 1/5] arm: qmp: add GICCapability struct Peter Xu
2016-03-22 18:29 ` Markus Armbruster
2016-03-22 18:41 ` Markus Armbruster
2016-03-23 2:58 ` Peter Xu
2016-03-23 9:33 ` Markus Armbruster
2016-03-23 11:48 ` Peter Xu
2016-03-23 12:21 ` Markus Armbruster
2016-03-23 14:25 ` Peter Xu
2016-03-23 15:17 ` Markus Armbruster
2016-03-24 2:27 ` Peter Xu
2016-03-22 18:32 ` Eric Blake
2016-03-23 3:09 ` Peter Xu
2016-03-23 9:44 ` Markus Armbruster
2016-03-23 11:56 ` Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 2/5] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-22 18:28 ` Markus Armbruster
2016-03-23 4:14 ` Peter Xu
2016-03-23 9:52 ` Markus Armbruster
2016-03-23 12:04 ` Peter Xu
2016-03-23 14:06 ` Markus Armbruster
2016-03-23 14:31 ` Eric Blake
2016-03-22 18:42 ` Eric Blake
2016-03-22 19:09 ` Markus Armbruster
2016-03-23 4:07 ` Peter Xu
2016-03-23 9:54 ` Markus Armbruster
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 3/5] arm: enhance kvm_arm_create_scratch_host_vcpu Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 4/5] kvm: add kvm_support_device() helper function Peter Xu
2016-03-18 3:27 ` [Qemu-devel] [PATCH v5 5/5] arm: implement query-gic-capabilities Peter Xu
2016-03-21 15:56 ` [Qemu-devel] [PATCH v5 0/5] ARM: add query-gic-capabilities SMP command Andrea Bolognani
2016-03-22 2:23 ` Peter Xu [this message]
2016-03-22 14:20 ` Markus Armbruster
2016-03-23 5:19 ` Peter Xu
2016-03-22 14:49 ` Peter Maydell
2016-03-23 5:43 ` 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=20160322022327.GA26867@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).