From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com
Subject: [Qemu-devel] [PATCH 0/9] virtio: device configuration cleanup
Date: Thu, 24 Nov 2011 13:38:19 +0100 [thread overview]
Message-ID: <1322138308-31040-1-git-send-email-pbonzini@redhat.com> (raw)
This series cleans up device configuration in virtio:
1) all properties (features and not) are moved to a single macro
DEFINE_VIRTIO_XYZ_PROPERTIES. This makes the definitions
uniform across all three virtio backends.
2) all configuration is moved to a single struct, which embeds
the NICConf/BlockConf for respectively virtio-nic/virtio-blk.
This lets the DEFINE_VIRTIO_XYZ_PROPERTIES include these
pieces as well.
3) virtio-9p had some knowledge of PCI, but there should be
no reason why s390 or mmio backends cannot use it. These bits
are removed and moved back to virtio-pci.[ch].
Tested x86_64, compiled arm+s390x.
Paolo Bonzini (9):
virtio-net: move property declarations to header file
virtio-net: move NICConf into virtio_net_conf
virtio-serial: move property declarations to header file
virtio-9p: remove PCI dependencies from hw/9pfs/
virtio-9p: move property declarations to header file
virtio-blk: define VirtIOBlkConf
virtio-blk: move property declarations to header file
virtio-blk: move BlockConf into VirtIOBlkConf
virtio: move conf fields into an anonymous union
hw/9pfs/virtio-9p-device.c | 35 +---------------------
hw/{9p.h => 9pfs/virtio-9p-device.h} | 9 ++++-
hw/9pfs/virtio-9p.c | 1 -
hw/s390-virtio-bus.c | 18 +++--------
hw/s390-virtio-bus.h | 11 ++++---
hw/syborg_virtio.c | 15 +++------
hw/virtio-blk.c | 28 ++++++++--------
hw/virtio-blk.h | 12 +++++++
hw/virtio-net.c | 13 ++++----
hw/virtio-net.h | 43 +++++++++++++++------------
hw/virtio-pci.c | 55 +++++++++++++++++++++++----------
hw/virtio-pci.h | 14 +++++----
hw/virtio-serial.h | 5 +++
hw/virtio.h | 9 ++---
14 files changed, 135 insertions(+), 133 deletions(-)
rename hw/{9p.h => 9pfs/virtio-9p-device.h} (50%)
--
1.7.7.1
next reply other threads:[~2011-11-24 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 12:38 Paolo Bonzini [this message]
2011-11-24 12:38 ` [Qemu-devel] [PATCH 1/9] virtio-net: move property declarations to header file Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 2/9] virtio-net: move NICConf into virtio_net_conf Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 3/9] virtio-serial: move property declarations to header file Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 4/9] virtio-9p: remove PCI dependencies from hw/9pfs/ Paolo Bonzini
2011-11-28 17:18 ` Aneesh Kumar K.V
2011-11-28 18:46 ` Michael S. Tsirkin
2011-11-29 8:38 ` Paolo Bonzini
2011-11-29 13:12 ` Michael S. Tsirkin
2012-01-01 21:45 ` Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 5/9] virtio-9p: move property declarations to header file Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 6/9] virtio-blk: define VirtIOBlkConf Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 7/9] virtio-blk: move property declarations to header file Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 8/9] virtio-blk: move BlockConf into VirtIOBlkConf Paolo Bonzini
2011-11-24 12:38 ` [Qemu-devel] [PATCH 9/9] virtio: move conf fields into an anonymous union Paolo Bonzini
2011-11-28 18:51 ` [Qemu-devel] [PATCH 0/9] virtio: device configuration cleanup Michael S. Tsirkin
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=1322138308-31040-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=mst@redhat.com \
--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).