|
From: | Evgeny Voevodin |
Subject: | Re: [Qemu-devel] [RFC 0/9] Virtio-mmio refactoring. |
Date: | Fri, 04 May 2012 07:41:52 +0400 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 |
On 03.05.2012 16:14, Peter Maydell wrote:
On 25 April 2012 06:54, Evgeny Voevodin<address@hidden> wrote:In this patchset refactoring of virtio-mmio layer is made. Instead of creating virtio-blk-mmio, virtio-net-mmio, etc on the system bus we create virtio-blk, virtio-net, etc devices on the virtio-transport bus. To create virtio-transport bus virtio-mmio-transport device provided. Transport device plugs into virtio-mmio bus. To create virtio-mmio bus virtio-mmio-bridge device provided.This seems to me to have one more layer than it needs. Why not just: create virtio-blk, virtio-net, etc on the virtio-transport bus To create virtio-transport bus, we create a virtio-mmio-transport device, and this device is a sysbus device. ie why do you have separate "virtio-mmio-transport" and "virtio-mmio-bridge" devices, and two different new buses ("virtio-mmio" and "virtio-transport") rather than just "virtio-transport"? -- PMM
Actually, the only necessity to have a bridge device is to count amount of transport devices. Amount of transport devices we need to know becausewe want to specify names to transport buses (virtio-mmio.0, virtio-mmio.1, ...). If there is a way to find out amount of transport devices on sysbus (and on pci bus)
we don't need bridge device.Maybe, there is also another way to specify bus names instead of just get parent bus name
and add transport device's index as a tail. -- Kind regards, Evgeny Voevodin, Leading Software Engineer, ASWG, Moscow R&D center, Samsung Electronics e-mail: address@hidden
[Prev in Thread] | Current Thread | [Next in Thread] |