From: Elliott Mitchell <ehem+xen@m5p.com>
To: xen-devel@lists.xenproject.org
Cc: Anthony PERARD <anthony.perard@vates.tech>
Cc: Juergen Gross <jgross@suse.com>
Subject: [PATCH 0/5] Some cleanup of libxl JSON handling
Date: Wed, 14 Oct 2026 15:31:49 -0700 [thread overview]
Message-ID: <cover.1792017109.git.ehem+xen@m5p.com> (raw)
Another batch which has been hanging around for a while and never
submitted. Here the observation is most of the data passed to the JSON
libraries aren't modified. Marking the arguments to the functions as
constant is correct and makes the API rather similar to the one used
for "SXP". Once that is done some more merging is possible.
There seems to be a bit of a difference in how the interface for
libjson-c is formatted versus the libyajl variant. I've left it similar
to how it appeared to be done, but that looks a bit odd. If there is a
desire for linebreaks and indentation feel free.
This has been rebased for the new libjson-c library. Only difference was
needing to add some duplicate hunks for the new library.
Elliott Mitchell (5):
tools/libxl: Mark pointer args of many functions constant
tools/xl: Mark libxl_domain_config * arg of printf_info_*() const
tools/libxl: Tiny optimization of libxl__mac_is_default()
tools/xl: Rename printf_info()/list_domains_details() to dump_by_...()
tools/xl: Merge down debug/dry-run section of create_domain()
tools/include/libxl_json.h | 38 ++++++++++++++++---------------
tools/libs/light/gentypes.py | 12 +++++-----
tools/libs/light/libxl_cpuid.c | 7 +++---
tools/libs/light/libxl_internal.c | 8 +++----
tools/libs/light/libxl_internal.h | 18 +++++++--------
tools/libs/light/libxl_json.c | 33 ++++++++++++++-------------
tools/libs/light/libxl_nocpuid.c | 4 ++--
tools/xl/xl.h | 13 +++++++----
tools/xl/xl_info.c | 33 +++++++++++++++------------
tools/xl/xl_misc.c | 2 +-
tools/xl/xl_sxp.c | 6 ++---
tools/xl/xl_vmcontrol.c | 14 +-----------
12 files changed, 95 insertions(+), 93 deletions(-)
--
2.47.3
next reply other threads:[~2026-10-15 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 22:31 Elliott Mitchell [this message]
2026-10-14 22:31 ` [PATCH 1/5] tools/libxl: Mark pointer args of many functions constant Elliott Mitchell
2026-10-14 22:31 ` [PATCH 4/5] tools/xl: Rename printf_info()/list_domains_details() to dump_by_...() Elliott Mitchell
2026-10-14 22:31 ` [PATCH 5/5] tools/xl: Merge down debug/dry-run section of create_domain() Elliott Mitchell
2026-10-14 22:31 ` [PATCH 3/5] tools/libxl: Tiny optimization of libxl__mac_is_default() Elliott Mitchell
2026-10-14 22:31 ` [PATCH 2/5] tools/xl: Mark libxl_domain_config * arg of printf_info_*() const Elliott Mitchell
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=cover.1792017109.git.ehem+xen@m5p.com \
--to=ehem+xen@m5p.com \
--cc=anthony.perard@vates.tech \
--cc=xen-devel@lists.xenproject.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 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.