From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
patches@linaro.org, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>,
kvmarm@lists.cs.columbia.edu,
KONRAD Frederic <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] [PATCH 0/8] Add virtio-mmio and use it in vexpress
Date: Mon, 8 Jul 2013 14:08:31 +0100 [thread overview]
Message-ID: <CAFEAcA8JAMeTKNwQakGGfTeYOc8BiScx6V1kNV3Jk5ACpf1C1Q@mail.gmail.com> (raw)
In-Reply-To: <39E5AB85-E7DD-4B9F-9F6F-F80CA6FCAC11@suse.de>
On 8 July 2013 13:59, Alexander Graf <agraf@suse.de> wrote:
> On 08.07.2013, at 14:57, Alexander Graf wrote:
>> On 27.06.2013, at 15:04, Peter Maydell wrote:
>>> The basic idea is that the board instantiates some transports,
>>
>> I really dislike that idea. Couldn't you also create a new
>> bus for your vexpress platform and add a virtio-mmio-vexpress
>> device that automatically allocates an interrupt from the main
>> PIC on instantiation? That way you could create transports
>> using -device.
This doesn't seem to gain anything except that the user has
to use -device twice rather than once.
>> Combine that with automatic fdt generation and you get fully
>> command line scaling device creation.
>
> Ah, you already have the fdt generation bit. So you're really
> only missing the automatic irq allocation to make it actually
> user friendly and flexible.
It's not clear to me how you can automatically allocate an IRQ:
there just aren't that many available, and I'm already a bit
nervous about stealing 4, because we might run into issues if
newer versions of h/w use those IRQs for something else. One
approach would be to have all virtio transports share an IRQ
line (the spec currently forbids this; I need to test if it
would actually work in practice...)
As far as I know there's no way to find out at board
construction how many virtio devices you might want.
thanks
-- PMM
next prev parent reply other threads:[~2013-07-08 13:31 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 [this message]
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
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=CAFEAcA8JAMeTKNwQakGGfTeYOc8BiScx6V1kNV3Jk5ACpf1C1Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=fred.konrad@greensocs.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@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 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).