From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: kdump with xen-unstable on efi machine
Date: Thu, 27 Nov 2014 09:49:28 +0000 [thread overview]
Message-ID: <1417081768.11944.70.camel@citrix.com> (raw)
In-Reply-To: <5475E311.6070501@citrix.com>
On Wed, 2014-11-26 at 14:26 +0000, Andrew Cooper wrote:
> libxc (or some new alternative) should suck it up and gain some notion
> of a stable API or ABI (like the rest of the world appears to be able to
> manage), such that it is possible to compile with an older header and
> use a newer .so at runtime.
Retrofitting a stable API/ABI to the melting pot which is libxc simply
isn't going to work in practice.
IMO the most likely to succeed approach would be to split off the bits
of libxc which 3rd party's can/should/need to rely on into one of more
libraries, probably by functional area.
So far I'm aware of plans (or at least desires) to do that for:
* Interfaces used by device-models/qemu.
* The bits which are useful inside a guest (i.e. the
various /dev/xen/* related helpers).
So it sounds like libxenkexec should be added to that list.
Ian.
next prev parent reply other threads:[~2014-11-27 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 12:15 kdump with xen-unstable on efi machine Juergen Gross
2014-11-26 12:41 ` Andrew Cooper
2014-11-26 14:01 ` Juergen Gross
2014-11-26 14:26 ` Andrew Cooper
2014-11-27 9:49 ` Ian Campbell [this message]
2014-11-27 11:05 ` Andrew Cooper
2014-11-27 11:32 ` Ian Campbell
2014-11-27 11:51 ` Andrew Cooper
2014-11-26 14:30 ` Konrad Rzeszutek Wilk
2014-11-26 14:49 ` Juergen Gross
2014-11-27 0:19 ` Daniel Kiper
2014-11-27 5:40 ` Juergen Gross
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=1417081768.11944.70.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xensource.com \
/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.