[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU
From: |
Paul Brook |
Subject: |
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU |
Date: |
Mon, 11 May 2009 17:43:54 +0100 |
User-agent: |
KMail/1.9.9 |
> > I'm not convinced virtio is as much of a separate entity as you think it
> > is. It's certainly not a bus. It's an implementation detail that happens
> > to be shared by several devices.
>
> It is once you abstract out the transport API from the transport
> implementation. We fall short here in QEMU today mainly for better
> integration with how machines are created today. I'd like to refactor
> the QEMU virtio code though to be closer to the Linux side of things. I
> see a module mechanism like this as a prereq for doing such a refactoring.
I think it's only a prerequisite if you want a single "virtio" device that
then magically morphs into a specific device based on its config. In
practice I don't think this is really useful, and the virtio init is driven
directly from the host binding. i.e. you have separate virtio-net-pci,
virtio-blk-pci, virtio-net-s390, etc. devices in the same way that other pci
devices are top level entities.
I've already got a patch I'm hoping to push out soon that implements a
different virtio binding.
Paul
- Re: [Qemu-devel] [PATCH 4/4] Introduce global .config to selectively enable compile features, (continued)
[Qemu-devel] [PATCH 3/4] Move block drivers into their own directory, Anthony Liguori, 2009/05/11
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU, Paul Brook, 2009/05/11
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU, Anthony Liguori, 2009/05/11
Message not available