qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH v2 0/7] qom: misc fixes & enhancements to support TLS work
Date: Thu, 30 Apr 2015 16:46:31 +0100	[thread overview]
Message-ID: <1430408798-20914-1-git-send-email-berrange@redhat.com> (raw)

This series contains the 7 generic QOM API fixes and enhancements
that I previously posted as part of the large series refactoring
and extending the TLS support in QEMU:

  https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg02038.html

I'm sending it separately, since the patches are reasonably well
self-contained and thus hopefully suitable for quicker review and
merge.

Changed in v2:

 - Pass "Object * parent" instead of "char *path" paremeter
 - Rely on stable reference from parent to keep new object alive
 - Use object_unparent() where appropriate

Daniel P. Berrange (7):
  qom: fix typename of 'policy' enum property in hostmem obj
  qom: document user creatable object types in help text
  qom: create objects in two phases
  qom: add object_new_propv / object_new_proplist constructors
  qom: make enum string tables const-correct
  qom: add a object_property_add_enum helper method
  qom: don't pass string table to object_get_enum method

 backends/hostmem.c          |  22 ++--
 include/hw/qdev-core.h      |   2 +-
 include/qapi/util.h         |   2 +-
 include/qapi/visitor-impl.h |   6 +-
 include/qapi/visitor.h      |   2 +-
 include/qom/object.h        |  87 ++++++++++++-
 numa.c                      |   2 +-
 qapi/qapi-dealloc-visitor.c |   3 +-
 qapi/qapi-util.c            |   2 +-
 qapi/qapi-visit-core.c      |   6 +-
 qemu-options.hx             |  70 +++++++---
 qom/object.c                | 145 ++++++++++++++++++++-
 scripts/qapi-types.py       |   4 +-
 tests/.gitignore            |   1 +
 tests/Makefile              |   5 +-
 tests/check-qom-proplist.c  | 308 ++++++++++++++++++++++++++++++++++++++++++++
 vl.c                        |  40 +++++-
 17 files changed, 657 insertions(+), 50 deletions(-)
 create mode 100644 tests/check-qom-proplist.c

-- 
2.1.0

             reply	other threads:[~2015-04-30 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 15:46 Daniel P. Berrange [this message]
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 1/7] qom: fix typename of 'policy' enum property in hostmem obj Daniel P. Berrange
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 2/7] qom: document user creatable object types in help text Daniel P. Berrange
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 3/7] qom: create objects in two phases Daniel P. Berrange
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 4/7] qom: add object_new_propv / object_new_proplist constructors Daniel P. Berrange
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 5/7] qom: make enum string tables const-correct Daniel P. Berrange
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 6/7] qom: add a object_property_add_enum helper method Daniel P. Berrange
2015-05-01 10:28   ` Daniel P. Berrange
2015-04-30 15:46 ` [Qemu-devel] [PATCH v2 7/7] qom: don't pass string table to object_get_enum method Daniel P. Berrange

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=1430408798-20914-1-git-send-email-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=afaerber@suse.de \
    --cc=pbonzini@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).