Re: [Qemu-devel] Virtio refactoring.

[Cornelia Huck <cornelia.huck@de.ibm.com>]

On Tue, 13 Nov 2012 17:31:40 +0100
KONRAD Frédéric <fred.konrad@greensocs.com> wrote:

> On 13/11/2012 16:32, Cornelia Huck wrote:
> > On Tue, 13 Nov 2012 15:27:57 +0100
> > KONRAD Frédéric <fred.konrad@greensocs.com> wrote:
> >
> >> To fix this, an idea is to use a new qbus named VirtioBus to link virtio-pci
> >> or virtio-mmio with all the virtio backend ( VirtioDevice ). So
> >> "virtio-pci" and
> >> "virtio-mmio" will have a VirtioBus.
> > Just to spell this out:
> >
> > We'd go from
> >
> > system bus
> > -> virtio transport bridge dev (virtio-xxx-bridge)
> >     -> virtio transport bus (virtio-xxx-bus)
> >        -> virtio transport dev (virtio-<type>-xxx)
> >
> > to
> >
> > system bus
> > -> virtio transport bridge dev (virtio-bridge-xxx)
> >     -> virtio bus (virtio-bus-xxx)
> >        -> virtio dev (virtio-<type>-xxx)
> >
> > ?
> I'm not sure of what you mean,.. do you mean for s390 ?
> 
> for the moment we have e.g : virtio-blk-pci ( in virtio-pci.c )
> 
> and we want virtio-pci -> virtio-bus -> virtio-blk.
> 
> ( or virtio-mmio -> virtio-bus -> virtio-blk. for pci-less system. )

I meant the structure you see in 'info qtree'. We might be talking
about the same thing :)

> >> Is it the right approach ? Do I miss something ?
> > What of the alias handling? Can this be killed once everything has been
> > converted?
> Which alias ?

The alias stuff in hw/qdev-monitor.c that lets you specify either
virtio-<type>-<transport> or virtio-<type>.