From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Christoffer Dall <christoffer.dall@linaro.org>
Cc: Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>,
kvmarm@lists.cs.columbia.edu, qemu-devel@nongnu.org,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 0/8] Add virtio-mmio and use it in vexpress
Date: Wed, 17 Jul 2013 07:41:50 -0500 [thread overview]
Message-ID: <87k3kpicj5.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA8qNfAumPw=u0t3fh23Fn6GCcVdX5G4MEdQY60WPTBv3A@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 17 July 2013 10:30, Christoffer Dall <christoffer.dall@linaro.org> wrote:
>> I'm not familiar enough with QEMU internals to intelligently comment on
>> this discussion, but I do have two observations:
>>
>> (1) It would be tremendously beneficial to have this patch series
>> merged, so people can actually start to have upstream code that supports
>> usable VMs on ARM, and it doesn't seem too invasive to me.
>
> Well, v3 of the patchset rather than this one, but yes.
> Anthony -- are you going to apply it directly (at some point,
> v3 has only been on list a day or so) as virtio maintainer,
> or should I put it in via arm-devs?
I would be happy for it to go through arm-devs and for any future
changes to virtio-mmio to go through that tree.
Regards,
Anthony Liguori
>
> thanks
> -- PMM
prev parent reply other threads:[~2013-07-17 12:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 13:04 [Qemu-devel] [PATCH 0/8] Add virtio-mmio and use it in vexpress Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 1/8] device_tree: Add qemu_devtree_setprop_sized_cells() utility functions Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 2/8] arm/boot: Use qemu_devtree_setprop_sized_cells() Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 3/8] virtio: Add support for guest setting of queue size Peter Maydell
2013-07-08 19:39 ` Anthony Liguori
2013-07-09 8:27 ` Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 4/8] virtio: Support transports which can specify the vring alignment Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 5/8] virtio: Implement MMIO based virtio transport Peter Maydell
2013-07-08 19:52 ` Anthony Liguori
2013-06-27 13:04 ` [Qemu-devel] [PATCH 6/8] arm/boot: Allow boards to modify the FDT blob Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 7/8] vexpress: Make VEDBoardInfo extend arm_boot_info Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 8/8] vexpress: Add virtio-mmio transports Peter Maydell
2013-07-08 12:57 ` [Qemu-devel] [PATCH 0/8] Add virtio-mmio and use it in vexpress Alexander Graf
2013-07-08 12:59 ` Alexander Graf
2013-07-08 13:08 ` Peter Maydell
2013-07-08 13:16 ` Alexander Graf
2013-07-08 13:23 ` Peter Maydell
2013-07-08 13:45 ` Alexander Graf
2013-07-08 14:06 ` Peter Maydell
2013-07-08 20:08 ` Anthony Liguori
2013-07-08 20:47 ` Alexander Graf
2013-07-08 21:06 ` Anthony Liguori
2013-07-09 9:28 ` Andreas Färber
2013-07-10 10:56 ` Alexander Graf
2013-07-17 9:30 ` Christoffer Dall
2013-07-17 9:34 ` Peter Maydell
2013-07-17 12:41 ` Anthony Liguori [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=87k3kpicj5.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.