From: Ian Campbell <ian.campbell@citrix.com>
To: Alex Braunegg <alex.braunegg@gmail.com>, xen-devel@lists.xen.org
Cc: 'Ian Jackson' <Ian.Jackson@eu.citrix.com>,
'Wei Liu' <wei.liu2@citrix.com>,
'Jan Beulich' <JBeulich@suse.com>,
'Andrew Cooper' <Andrew.Cooper3@citrix.com>
Subject: Re: [BUG} libxl.c:5947:libxl_send_trigger: Send trigger 'reset' failed: Function not implemented
Date: Thu, 11 Feb 2016 09:33:25 +0000 [thread overview]
Message-ID: <1455183205.814.5.camel@citrix.com> (raw)
In-Reply-To: <56bbba08.ee35420a.d8138.fffff636@mx.google.com>
On Thu, 2016-02-11 at 09:30 +1100, Alex Braunegg wrote:
> So potentially before trying to make use of libxl__domain_pvcontrol for
> the 'xl vm-list' command to provide feedback if PV control is available,
> I will need to wait for the functionality to be exposed via an applicable
> libxl header.
Yes, exposing an internal function in the public API generally involves:
* renaming into the libxl_foo rather than libxl__foo namespace and moving
the prototype to libxl.h. Perhaps giving it a more "public" API friendly
name and checking that the API is sane enough to be maintained in an API
compatible manner going forward (this one seems simple enough to be
sane).
* Adjusting the function to take a libxl_ctx *ctx instead of a libxl__gc
*gc, which involves adding GC_INIT and GC_FREE in the function itself.
This will require ensuring the function has a single exit path which
calls GC_FREE (see also tools/libxl/CODING_STYLE)
* Adding a LIBXL_HAVE... to libxl.h to indicate to 3rd party applications
that this functionality is available (nothing in xen.git should be
conditional on this #define though)
* Updating xl to use this new functionality
Patches welcome.
Ian.
next prev parent reply other threads:[~2016-02-11 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:50 [BUG} libxl.c:5947:libxl_send_trigger: Send trigger 'reset' failed: Function not implemented Alex Braunegg
2016-02-04 10:57 ` Ian Campbell
2016-02-04 23:08 ` Alex Braunegg
2016-02-09 10:28 ` Ian Campbell
2016-02-10 0:51 ` Alex Braunegg
2016-02-10 9:32 ` Ian Campbell
2016-02-10 22:30 ` Alex Braunegg
2016-02-11 9:33 ` Ian Campbell [this message]
2016-02-08 21:48 ` Alex Braunegg
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=1455183205.814.5.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=alex.braunegg@gmail.com \
--cc=wei.liu2@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).