From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: anthony.perard@citrix.com, stefano.stabellini@eu.citrix.com,
Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl: add option for discard support to xl disk configuration
Date: Wed, 29 Jan 2014 17:07:17 +0100 [thread overview]
Message-ID: <20140129160717.GA11100@aepfle.de> (raw)
In-Reply-To: <1391011264.31814.134.camel@kazak.uk.xensource.com>
On Wed, Jan 29, Ian Campbell wrote:
> On Wed, 2014-01-29 at 16:06 +0100, Olaf Hering wrote:
> > This new field changes the API, _libxl_types.h:struct libxl_device_disk
> > gets a new member. How should code using this new flag recognize if its
> > present? If it is supposed to be part of a new libxl-4.5 API then
> > out-of-tree code could put the code into #ifdef LIBXL_API_VERSION >= X.
> > If not, how should it be done?
> You should add a #define LIBXL_HAVE_FOO to libxl.h, there are a few
> examples in there already.
I will add such a define.
> There is no need to make the actual field conditional -- that would
> actually be wrong since it would modify the ABI depending on what the
> application asked for, meaning it would differ from how libxl was
> actually built. An application which us using an ABI before 4.5 simply
> won't think to touch this field.
I meant the access of the field in libvirt, like "p->discard_enable = val;".
Putting such code into #ifdef LIBXL_HAVE_FOO is fine.
Olaf
next prev parent reply other threads:[~2014-01-29 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 18:24 [PATCH] libxl: add option for discard support to xl disk configuration Olaf Hering
2014-01-28 18:26 ` [PATCH] qemu-upstream: add discard support for xen_disk Olaf Hering
2014-01-28 20:10 ` Stefano Stabellini
2014-01-29 10:30 ` Ian Campbell
2014-01-29 10:28 ` [PATCH] libxl: add option for discard support to xl disk configuration Ian Campbell
2014-01-29 11:19 ` Olaf Hering
2014-01-29 11:45 ` Ian Campbell
2014-01-29 14:23 ` Olaf Hering
2014-01-29 18:24 ` Olaf Hering
2014-01-30 10:56 ` Olaf Hering
2014-01-30 11:07 ` Ian Campbell
2014-01-29 15:06 ` Olaf Hering
2014-01-29 16:01 ` Ian Campbell
2014-01-29 16:07 ` Olaf Hering [this message]
2014-01-29 16:19 ` Ian Campbell
2014-01-30 11:32 ` Ian Jackson
2014-01-30 11:36 ` Ian Campbell
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=20140129160717.GA11100@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=stefano.stabellini@eu.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 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.