On Thu, 15 Nov 2012 11:32:13 +0100
KONRAD Frédéric wrote:
> For the qtree structure we have eg for virtio block :
>
> bus: main-system-bus
>type System
>dev: pcihost, id ""
> bus: pci.0
>type PCI
>dev: virtio-blk-pci, id ""
> ...
>
My current virtio-ccw l
Hi,
On 13/11/2012 19:09, Cornelia Huck wrote:
On Tue, 13 Nov 2012 17:31:40 +0100
KONRAD Frédéric wrote:
We'd go from
system bus
-> virtio transport bridge dev (virtio-xxx-bridge)
-> virtio transport bus (virtio-xxx-bus)
-> virtio transport dev (virtio--xxx)
to
system bus
-> vi
Am 13.11.2012 16:32, schrieb Cornelia Huck:
> On Tue, 13 Nov 2012 15:27:57 +0100
> KONRAD Frédéric wrote:
>> * Introduce a new VirtioBus ( same way as scsi-bus.c ), with
>> VirtIODevice
>>interface :
>> -> callback to completely abstract the VirtioDevice from
>> VirtioPCI.
On Tue, 13 Nov 2012 17:31:40 +0100
KONRAD Frédéric wrote:
> On 13/11/2012 16:32, Cornelia Huck wrote:
> > On Tue, 13 Nov 2012 15:27:57 +0100
> > KONRAD Frédéric wrote:
> >
> >> To fix this, an idea is to use a new qbus named VirtioBus to link
> >> virtio-pci
> >> or virtio-mmio with all the vir
On 13/11/2012 16:32, Cornelia Huck wrote:
On Tue, 13 Nov 2012 15:27:57 +0100
KONRAD Frédéric 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.
On Tue, 13 Nov 2012 15:27:57 +0100
KONRAD Frédéric 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 f
Hi,
Just to be sure that we are all understanding the same thing about the
virtio
refactoring.
The old patch-set ( git://git.greensocs.com/qemu_virtio.git virtio ) I
sent was
not good because :
* It use a custom transport property ( e.g : transport=virtio-mmio.0 ) for
selecting a transpor
