From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org
Cc: Wei Liu <wei.liu2@citrix.com>,
ian.jackson@eu.citrix.com, ian.campbell@citrix.com
Subject: [PATCH RFC V2 00/10] xl/libxl: JSON infrastructure and new "xl-json" format
Date: Thu, 17 Apr 2014 12:13:01 +0100 [thread overview]
Message-ID: <1397733191-31892-1-git-send-email-wei.liu2@citrix.com> (raw)
This series contains my original patches to add in JSON parser and a new patch
to add "xl-json" format. The last patch makes use of JSON parser.
For the JSON parser (taken from my previous email):
Libxl introduced JSON infrastructure to communicate with upstream QEMU. The
ability of exisiting JSON infrastructure is to convert libxl_FOO struct to
libxl JSON object and parse JSON object (string) returned by QEMU.
This series makes libxl able to convert a JSON string to libxl_FOO struct.
The conversion is done in two macro steps:
1. convert JSON string to libxl JSON object (libxl__json_object)
2. convert libxl JSON object to libxl_FOO struct
The first stage is done with existing infrastructure. This series focuses on
the second stage.
To break things down:
* Patch 1 is only mechanical change
* Patch 2, 3, 4 and 6 are changes to generic libxl JSON infrastructure
* Patch 5 introduces parser functions for builtin types
* Patch 7 and 8 are changes to code generator
* Patch 9 contains changes to test code generator
Now we have the ability to do the following transformation:
libxl_FOO struct -> libxl_FOO JSON object -> libxl JSON internal object ->
libxl_FOO struct
This full cycle can be used to preserved runtime configurations of a domain.
Patch 10 makes use of the new parser and introduces "xl-json" format. Please
refer to commit log for details. It would be good if I can get some input on
this new format and it's usage. Currently it's restricted to internal use only,
that is, user is not allowed to supply a config file in JSON format.
It would be good if we can get this kind of infrastructure change through the
push gate before pursing next step ("pull runtime information for a domain").
Wei.
Changes in V2:
* address IanC's comments on JSON parser
* add "xl-json" format patch
Wei Liu (10):
libxl IDL: rename json_fn to json_gen_fn
libxl_json: introduce libx__object_from_json
libxl_internal: make JSON_* types bit-field
libxl_internal: introduce libxl__json_object_is_{null,number,double}
libxl_json: introduce parser functions for builtin types
libxl_json: allow basic JSON type objects generation
libxl/gentypes.py: generate JSON object for keyed-union discriminator
libxl IDL: generate code to parse libxl__json_object to libxl_FOO
struct
libxl/gentest.py: test JSON parser
xl: introduce "xl-json" format
docs/man/xl.cfg.pod.5 | 2 +-
tools/libxl/gentest.py | 27 +++-
tools/libxl/gentypes.py | 119 ++++++++++++++-
tools/libxl/idl.py | 23 ++-
tools/libxl/libxl.h | 1 +
tools/libxl/libxl_cpuid.c | 92 +++++++++---
tools/libxl/libxl_internal.h | 39 +++--
tools/libxl/libxl_json.c | 263 ++++++++++++++++++++++++++++++++--
tools/libxl/libxl_json.h | 27 +++-
tools/libxl/libxl_nocpuid.c | 7 +
tools/libxl/libxl_types.idl | 31 ++--
tools/libxl/libxl_types_internal.idl | 4 +-
tools/libxl/xl_cmdimpl.c | 103 ++++++++++---
13 files changed, 649 insertions(+), 89 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-04-17 11:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 11:13 Wei Liu [this message]
2014-04-17 11:13 ` [PATCH RFC V2 01/10] libxl IDL: rename json_fn to json_gen_fn Wei Liu
2014-04-17 11:13 ` [PATCH RFC V2 02/10] libxl_json: introduce libx__object_from_json Wei Liu
2014-04-22 14:49 ` Ian Campbell
2014-04-17 11:13 ` [PATCH RFC V2 03/10] libxl_internal: make JSON_* types bit-field Wei Liu
2014-04-22 14:50 ` Ian Campbell
2014-04-17 11:13 ` [PATCH RFC V2 04/10] libxl_internal: introduce libxl__json_object_is_{null, number, double} Wei Liu
2014-04-17 11:13 ` [PATCH RFC V2 05/10] libxl_json: introduce parser functions for builtin types Wei Liu
2014-04-22 15:09 ` Ian Campbell
2014-04-23 10:01 ` Wei Liu
2014-04-23 10:12 ` Ian Campbell
2014-04-23 10:19 ` Wei Liu
2014-04-23 10:31 ` Ian Campbell
2014-04-23 10:42 ` Wei Liu
2014-04-23 11:14 ` Wei Liu
2014-04-23 11:41 ` Ian Campbell
2014-04-23 12:00 ` Wei Liu
2014-04-24 15:28 ` Ian Jackson
2014-04-23 15:20 ` Wei Liu
2014-04-24 15:29 ` Ian Jackson
2014-04-17 11:13 ` [PATCH RFC V2 06/10] libxl_json: allow basic JSON type objects generation Wei Liu
2014-04-22 15:22 ` Ian Campbell
2014-04-23 10:15 ` Wei Liu
2014-04-23 10:30 ` Ian Campbell
2014-04-23 10:36 ` Wei Liu
2014-04-23 11:39 ` Ian Campbell
2014-04-17 11:13 ` [PATCH RFC V2 07/10] libxl/gentypes.py: generate JSON object for keyed-union discriminator Wei Liu
2014-04-22 15:27 ` Ian Campbell
2014-04-22 15:32 ` Wei Liu
2014-04-17 11:13 ` [PATCH RFC V2 08/10] libxl IDL: generate code to parse libxl__json_object to libxl_FOO struct Wei Liu
2014-04-22 15:46 ` Ian Campbell
2014-04-22 15:54 ` Wei Liu
2014-04-22 16:01 ` Ian Campbell
2014-04-22 16:12 ` Wei Liu
2014-04-17 11:13 ` [PATCH RFC V2 09/10] libxl/gentest.py: test JSON parser Wei Liu
2014-04-22 15:47 ` Ian Campbell
2014-04-22 15:49 ` Wei Liu
2014-04-22 15:58 ` Ian Campbell
2014-04-17 11:13 ` [PATCH RFC V2 10/10] xl: introduce "xl-json" format Wei Liu
2014-04-19 8:35 ` Wei Liu
2014-04-22 10:15 ` Ian Campbell
2014-04-22 10:25 ` Wei Liu
2014-04-22 10:33 ` Ian Campbell
2014-04-22 13:50 ` Ian Jackson
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=1397733191-31892-1-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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).