From: Nick Rosbrook <rosbrookn@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Nick Rosbrook <rosbrookn@ainfosec.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>
Subject: [PATCH 00/12] golang/xenlight: domain life cycle support
Date: Wed, 28 Apr 2021 20:14:22 -0400 [thread overview]
Message-ID: <cover.1619650820.git.rosbrookn@ainfosec.com> (raw)
The primary goal of this patch series is to allow users of the xenlight
package to manage a full domain life cycle. In particular, it provides
support for receiving domain death events so that domain shutdown,
reboot, destroy, etc. can be handled. And, it addresses issues found
when using the package to boot domains with various configurations.
These patches address several things (e.g. bug fixes, code style,
conveniences, new wrapper functions), but are all work towards the final
goal of allowing a package user to manage a full domain life cycle.
Nick Rosbrook (12):
golang/xenlight: update generated code
golang/xenlight: fix StringList toC conversion
golang/xenlight: fix string conversion in generated toC functions
golang/xenlight: export keyed union interface types
golang/xenlight: use struct pointers in keyed union fields
golang/xenlight: rename Ctx receivers to ctx
golang/xenlight: add logging conveniences for within xenlight
golang/xenlight: add functional options to configure Context
golang/xenlight: add DomainDestroy wrapper
golang/xenlight: add SendTrigger wrapper
golang/xenlight: do not negate ret when converting to Error
golang/xenlight: add NotifyDomainDeath method to Context
tools/golang/xenlight/gengotypes.py | 11 +-
tools/golang/xenlight/helpers.gen.go | 210 ++++++++++++--
tools/golang/xenlight/types.gen.go | 63 +++--
tools/golang/xenlight/xenlight.go | 395 ++++++++++++++++++++-------
4 files changed, 518 insertions(+), 161 deletions(-)
--
2.17.1
next reply other threads:[~2021-04-29 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 0:14 Nick Rosbrook [this message]
2021-04-29 0:14 ` [PATCH 01/12] golang/xenlight: update generated code Nick Rosbrook
2021-04-29 0:14 ` [PATCH 02/12] golang/xenlight: fix StringList toC conversion Nick Rosbrook
2021-04-29 0:14 ` [PATCH 03/12] golang/xenlight: fix string conversion in generated toC functions Nick Rosbrook
2021-04-29 0:14 ` [PATCH 04/12] golang/xenlight: export keyed union interface types Nick Rosbrook
2021-04-29 0:14 ` [PATCH 05/12] golang/xenlight: use struct pointers in keyed union fields Nick Rosbrook
2021-04-29 0:14 ` [PATCH 06/12] golang/xenlight: rename Ctx receivers to ctx Nick Rosbrook
2021-04-29 0:14 ` [PATCH 07/12] golang/xenlight: add logging conveniences for within xenlight Nick Rosbrook
2021-04-29 0:14 ` [PATCH 08/12] golang/xenlight: add functional options to configure Context Nick Rosbrook
2021-04-29 0:14 ` [PATCH 09/12] golang/xenlight: add DomainDestroy wrapper Nick Rosbrook
2021-04-29 0:14 ` [PATCH 10/12] golang/xenlight: add SendTrigger wrapper Nick Rosbrook
2021-04-29 0:14 ` [PATCH 11/12] golang/xenlight: do not negate ret when converting to Error Nick Rosbrook
2021-04-29 0:14 ` [PATCH 12/12] golang/xenlight: add NotifyDomainDeath method to Context 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.1619650820.git.rosbrookn@ainfosec.com \
--to=rosbrookn@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--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.