From: Nick Rosbrook <rosbrookn@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Nick Rosbrook <rosbrookn@ainfosec.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
george.dunlap@citrix.com, Wei Liu <wl@xen.org>
Subject: [RFC PATCH 0/2] add function support to IDL
Date: Mon, 27 Jul 2020 09:26:31 -0400 [thread overview]
Message-ID: <cover.1595854292.git.rosbrookn@ainfosec.com> (raw)
At a Xen Summit design session for the golang bindings (see [1]), we
agreed that it would be beneficial to expand the libxl IDL with function
support. In addition to benefiting libxl itself, this would allow other
language bindings to easily generate function wrappers.
These RFC patches outline a potential strategy for accomplishing this
goal. The first patch adds the Function and CtxFunction classes to
libxl/idl.py, introducing the idea of functions to the IDL. The second
patch adds a DeviceFunction class and adds some sample definitions to
libxl/libxl_types.idl for example purposes.
[1] https://lists.xenproject.org/archives/html/xen-devel/2020-07/msg00964.html
Nick Rosbrook (2):
libxl: add Function class to IDL
libxl: prototype libxl_device_nic_add/remove with IDL
tools/golang/xenlight/gengotypes.py | 2 +-
tools/libxl/gentypes.py | 2 +-
tools/libxl/idl.py | 54 ++++++++++++++++++++++++++++-
tools/libxl/libxl_types.idl | 6 ++++
4 files changed, 61 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-27 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:26 Nick Rosbrook [this message]
2020-07-27 13:26 ` [RFC PATCH 1/2] libxl: add Function class to IDL Nick Rosbrook
2020-08-14 10:52 ` Anthony PERARD
2020-08-17 15:26 ` Nick Rosbrook
2020-07-27 13:26 ` [RFC PATCH 2/2] libxl: prototype libxl_device_nic_add/remove with IDL Nick Rosbrook
2020-08-14 10:57 ` Anthony PERARD
2020-08-17 15:44 ` Nick Rosbrook
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.1595854292.git.rosbrookn@ainfosec.com \
--to=rosbrookn@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rosbrookn@ainfosec.com \
--cc=wl@xen.org \
--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.