From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
kraxel@redhat.com
Subject: [Qemu-devel] [PATCHv6 0/3] qemu: properties for feature compatibility
Date: Mon, 4 Jan 2010 18:08:05 +0200 [thread overview]
Message-ID: <20100104160805.GA15362@redhat.com> (raw)
Here's what I came up with for solving the problem of differences in
features in virtio between 0.12 and 0.11. This also enables migration
between different backends, e.g. between host where tap supports virtio
net header and where it does not: management just needs to set features
appropriately.
Compat bits are yet to be set, will be done when this patch is applied.
Changes since v5:
- added patch to rename features->guest_features
Changes since v4:
- Save bit offset in a separate field, offset is in bytes
Changes since RFC v2:
- we already have a flag to control write cache feature,
let's not add another one
Changes since RFC:
- add symbolic names for properties
- only optional features can be changed
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Michael S. Tsirkin (3):
qdev: add bit property type
virtio: rename features -> guest_features
virtio: add features as qdev properties
hw/qdev-properties.c | 62 ++++++++++++++++++++++++++++++++++++++++++++-----
hw/qdev.h | 11 +++++++++
hw/s390-virtio-bus.c | 14 ++++++++---
hw/s390-virtio-bus.h | 1 +
hw/syborg_virtio.c | 16 +++++++-----
hw/virtio-balloon.c | 4 +-
hw/virtio-blk.c | 6 +----
hw/virtio-blk.h | 8 ++++++
hw/virtio-console.c | 4 +-
hw/virtio-net.c | 49 +++++++++++++++++----------------------
hw/virtio-net.h | 20 ++++++++++++++++
hw/virtio-pci.c | 29 +++++++++++++++--------
hw/virtio.c | 10 ++++----
hw/virtio.h | 9 +++++-
14 files changed, 171 insertions(+), 72 deletions(-)
reply other threads:[~2010-01-04 16:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100104160805.GA15362@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@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).