qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: aliguori@us.ibm.com, i.mitsyanko@samsung.com,
	Evgeny Voevodin <e.voevodin@samsung.com>,
	qemu-devel@nongnu.org, kyungmin.park@samsung.com,
	d.solodkiy@samsung.com, m.kozlov@samsung.com
Subject: Re: [Qemu-devel] [RFC 0/9] Virtio-mmio refactoring.
Date: Fri, 04 May 2012 08:19:13 -0500	[thread overview]
Message-ID: <4FA3D751.80806@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA_S9wb-uTVRaye9c-=G4ZAN5+Z-BO3x1nnksrDj1UthRA@mail.gmail.com>

On 05/03/2012 07:14 AM, Peter Maydell wrote:
> On 25 April 2012 06:54, Evgeny Voevodin<e.voevodin@samsung.com>  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"?

I think using a bus won't work.   You need to create a VirtioDevice that has a 
link<VirtioTransport>.  I would suggest making VirtioTransport an interface.

Then you can have VirtioPCI inherit from PCIDevice and implement VirtioTransport.

Regards,

Anthony Liguori

>
> -- PMM
>

  parent reply	other threads:[~2012-05-04 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1335333257-5128-1-git-send-email-e.voevodin@samsung.com>
2012-05-03 12:14 ` [Qemu-devel] [RFC 0/9] Virtio-mmio refactoring Peter Maydell
2012-05-04  3:41   ` Evgeny Voevodin
2012-05-04 11:58     ` Evgeny Voevodin
2012-05-04 13:19   ` Anthony Liguori [this message]
2012-05-05  3:06     ` Evgeny Voevodin

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=4FA3D751.80806@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=d.solodkiy@samsung.com \
    --cc=e.voevodin@samsung.com \
    --cc=i.mitsyanko@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=m.kozlov@samsung.com \
    --cc=peter.maydell@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).