From: Luiz Capitulino <lcapitulino@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, armbru@redhat.com, mdroth@linux.vnet.ibm.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 0/3] add direct support of event in qapi schema
Date: Fri, 22 Nov 2013 09:33:28 -0500 [thread overview]
Message-ID: <20131122093328.397c376f@redhat.com> (raw)
In-Reply-To: <528EBB80.2010601@linux.vnet.ibm.com>
On Fri, 22 Nov 2013 10:03:44 +0800
Wenchao Xia <xiawenc@linux.vnet.ibm.com> wrote:
> 于 2013/11/13 9:44, Wenchao Xia 写道:
> > This series add support for tag/keyword 'event' in qapi-schema.
> > The implemention doesn't generate a struture and visit function
> > in the background for every event, so it doesn't support nested
> > structure in the define to avoid trouble.
> >
> > It is on top of series:
> > http://lists.nongnu.org/archive/html/qemu-devel/2013-11/msg01574.html
> >
> > Wenchao Xia (3):
> > 1 os-posix: include sys/time.h
> > 2 qapi script: add support of event
> > 3 tests: add test cases for qapi event support
> >
> > Makefile | 9 +-
> > Makefile.objs | 2 +-
> > include/sysemu/os-posix.h | 2 +
> > qapi/Makefile.objs | 1 +
> > scripts/qapi-event.py | 355 +++++++++++++++++++++++++++++++
> > tests/Makefile | 14 +-
> > tests/qapi-schema/qapi-schema-test.json | 12 +
> > tests/qapi-schema/qapi-schema-test.out | 10 +-
> > tests/test-qmp-event.c | 250 ++++++++++++++++++++++
> > 9 files changed, 646 insertions(+), 9 deletions(-)
> > create mode 100644 scripts/qapi-event.py
> > create mode 100644 tests/test-qmp-event.c
> >
> Luiz, do you think this series is in the right direction?
Sorry, but I haven't reviewed it yet. Will do it next week.
prev parent reply other threads:[~2013-11-22 14:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 1:44 [Qemu-devel] [PATCH RFC 0/3] add direct support of event in qapi schema Wenchao Xia
2013-11-13 1:44 ` [Qemu-devel] [PATCH RFC 1/3] os-posix: include sys/time.h Wenchao Xia
2013-12-13 13:26 ` Eric Blake
2013-11-13 1:44 ` [Qemu-devel] [PATCH RFC 2/3] qapi script: add support of event Wenchao Xia
2013-11-28 0:48 ` Luiz Capitulino
2013-11-28 7:16 ` Wenchao Xia
2013-11-28 14:31 ` Luiz Capitulino
2013-12-02 6:48 ` Wenchao Xia
2013-12-13 3:00 ` Wenchao Xia
2013-12-13 13:31 ` Eric Blake
2013-12-13 13:43 ` Kevin Wolf
2013-12-16 2:50 ` Wenchao Xia
2013-12-16 9:04 ` Markus Armbruster
2013-12-16 9:13 ` Markus Armbruster
2014-01-07 12:14 ` Markus Armbruster
2014-01-13 10:08 ` Markus Armbruster
2014-01-15 1:47 ` Wenchao Xia
2014-01-16 2:50 ` Michael Roth
2014-01-16 11:05 ` Paolo Bonzini
2014-01-30 10:35 ` Markus Armbruster
2013-12-16 2:51 ` Wenchao Xia
2013-11-13 1:44 ` [Qemu-devel] [PATCH 2/2] try Wenchao Xia
2013-11-13 1:47 ` Wenchao Xia
2013-11-13 1:44 ` [Qemu-devel] [PATCH RFC 3/3] tests: add test cases for qapi event support Wenchao Xia
2013-12-13 13:36 ` Eric Blake
2013-12-16 2:55 ` Wenchao Xia
2013-12-16 3:12 ` Wenchao Xia
2014-01-02 2:30 ` Wenchao Xia
2013-11-22 2:03 ` [Qemu-devel] [PATCH RFC 0/3] add direct support of event in qapi schema Wenchao Xia
2013-11-22 14:33 ` Luiz Capitulino [this message]
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=20131122093328.397c376f@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.