qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] add fixed-width visitors and serialization tests
Date: Wed, 22 Feb 2012 13:00:32 -0600	[thread overview]
Message-ID: <1329937236-6449-1-git-send-email-mdroth@linux.vnet.ibm.com> (raw)

These patches apply on top of qemu.git master, and can also be obtained from:
git://github.com/mdroth/qemu.git visitor-fixed-width-v1

These patches add fixed-width visitor types and switches all qdev users over to
them.

We also add a test suite which covers these as well as does some sanity
checking on Visitors which may be used in the future for serialization-type
use-cases.

I've also tried plugging in the new String-based visitors, but hit some test
failures due to how they handle floating point so I've held off on those while
I look into it more. That can be done in seperate patch though.

 hw/mc146818rtc.c             |    7 -
 hw/qdev-addr.c               |    4 +-
 hw/qdev-properties.c         |   42 +--
 qapi/qapi-visit-core.c       |  139 ++++++++
 qapi/qapi-visit-core.h       |   16 +
 test-visitor-serialization.c |  718 ++++++++++++++++++++++++++++++++++++++++++
 tests/Makefile               |    6 +-
 7 files changed, 897 insertions(+), 35 deletions(-)

             reply	other threads:[~2012-02-22 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 19:00 Michael Roth [this message]
2012-02-22 19:00 ` [Qemu-devel] [PATCH 1/3] qapi: add Visitor interfaces for uint*_t and int*_t Michael Roth
2012-02-22 19:00 ` [Qemu-devel] [PATCH 2/3] qapi: unit tests for visitor-based serialization Michael Roth
2012-02-22 19:00 ` [Qemu-devel] [PATCH 3/3] qdev: switch property accessors to fixed-width visitor interfaces Michael Roth

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=1329937236-6449-1-git-send-email-mdroth@linux.vnet.ibm.com \
    --to=mdroth@linux.vnet.ibm.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).