From: fred.konrad@greensocs.com
To: qemu-devel@nongnu.org, aliguori@us.ibm.com
Cc: cornelia.huck@de.ibm.com, peter.maydell@linaro.org,
mark.burton@greensocs.com, fred.konrad@greensocs.com
Subject: [Qemu-devel] [PATCH v4 0/7] virtio-refactoring cleanup.
Date: Wed, 24 Apr 2013 10:21:16 +0200 [thread overview]
Message-ID: <1366791683-5350-1-git-send-email-fred.konrad@greensocs.com> (raw)
From: KONRAD Frederic <fred.konrad@greensocs.com>
This is the last part of the refactoring.
The step 4 replaces the function pointers contained in VirtIODevice structure by
the function pointers contained in VirtioDeviceClass.
The step 5 removes virtiobindings, and use the VirtioBusClass.
I tested the changes on i386 only with virtio-blk on linux guest.
You can test here (it's on top of virtio-rng-v4 I sent earlier):
git://project.greensocs.com/qemu-virtio.git virtio-cleanup-v4
Changes v3 -> v4:
* Don't use device_plugged callback for s390 and ccw.
* Added unused prototype removing.
* Rebased.
Changes v2 -> v3:
* Fix PCI hot-unplug.
* Add CCW devices.
* A lot of rebasing.
Thanks,
Fred
KONRAD Frederic (7):
virtio-bus: add new functions.
virtio-bus: make virtio_x_bus_new static.
virtio-pci: cleanup.
virtio: remove the function pointer.
virtio: remove virtiobindings.
virtio: cleanup: init and exit function.
virtio: drop unused function prototypes.
hw/9pfs/virtio-9p-device.c | 2 -
hw/block/dataplane/virtio-blk.c | 15 +++---
hw/block/virtio-blk.c | 9 +---
hw/char/virtio-serial-bus.c | 8 +--
hw/net/vhost_net.c | 17 +++---
hw/net/virtio-net.c | 11 +---
hw/s390x/s390-virtio-bus.c | 21 +++-----
hw/s390x/s390-virtio-bus.h | 2 -
hw/s390x/virtio-ccw.c | 26 ++++------
hw/s390x/virtio-ccw.h | 2 -
hw/scsi/vhost-scsi.c | 18 +++----
hw/scsi/virtio-scsi.c | 8 +--
hw/virtio/vhost.c | 31 ++++++-----
hw/virtio/virtio-balloon.c | 8 +--
hw/virtio/virtio-bus.c | 40 ++++++++------
hw/virtio/virtio-pci.c | 112 +++++++++++-----------------------------
hw/virtio/virtio-pci.h | 3 --
hw/virtio/virtio-rng.c | 4 +-
hw/virtio/virtio.c | 109 +++++++++++++++++++-------------------
include/hw/virtio/virtio-bus.h | 9 ++--
include/hw/virtio/virtio.h | 59 +--------------------
21 files changed, 184 insertions(+), 330 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-04-24 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 8:21 fred.konrad [this message]
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 1/7] virtio-bus: add new functions fred.konrad
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 2/7] virtio-bus: make virtio_x_bus_new static fred.konrad
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 3/7] virtio-pci: cleanup fred.konrad
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 4/7] virtio: remove the function pointer fred.konrad
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 5/7] virtio: remove virtiobindings fred.konrad
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 6/7] virtio: cleanup: init and exit function fred.konrad
2013-04-24 8:21 ` [Qemu-devel] [PATCH v4 7/7] virtio: drop unused function prototypes fred.konrad
2013-04-24 18:24 ` [Qemu-devel] [PATCH v4 0/7] virtio-refactoring cleanup Anthony Liguori
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=1366791683-5350-1-git-send-email-fred.konrad@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=aliguori@us.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=mark.burton@greensocs.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).