Re: [RFC PATCH 06/13] Add MMIO based virtio transport

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 10.10.2012, at 10:33, Peter Maydell <peter.maydell@xxxxxxxxxx> wrote:

> On 10 October 2012 04:06, Christoffer Dall
> <c.dall@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> I'm trying to figure out how this is intended to work for both a
>> virtio block device and virtio net device. Can I use a single
>> transport device for both devices (with these patches this seems to
>> generate a segfault on qemu at startup) or am I supposed to define two
>> virtio-mmio-transport thingies, but then how does that get mapped in
>> terms of addresses?
> 
> The idea would be that the board model would (always) define a handful of
> transport devices at some convenient address and wire them up
> to suitable free interrupt lines. Then the user can choose to (or
> choose not to) plug in whichever virtio backend devices they want,
> when starting qemu.

Why not allocate them dynamically and populate the dt respectively?

Alex

> 
> -- PMM
> _______________________________________________
> kvmarm mailing list
> kvmarm@xxxxxxxxxxxxxxxxxxxxx
> https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm


[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux