From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
ian.jackson@eu.citrix.com, wei.liu2@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH RFC] tools: add map files for libxen{store, ctrl, guest}.so
Date: Thu, 7 Jan 2016 14:50:35 +0000 [thread overview]
Message-ID: <1452178235.21055.222.camel@citrix.com> (raw)
In-Reply-To: <568E77FE.1030104@citrix.com>
On Thu, 2016-01-07 at 14:36 +0000, Andrew Cooper wrote:
> On 07/01/16 13:51, Ian Campbell wrote:
> > The map files highlight a number of namespacing inconsistencies
> > (particularly with libxenguest using xc_* a significant amount).
> >
> > It also seems to highlight a bunch of libxenguest.so functionalty
> > which appears to want to be exported (xc_*) but is not used in tree.
> > The initial list was based on what was needed to compile everything in
> > tree. I then looked through the list for xc_* and checked if any were
> > exported in a public header, leading to adding the following functions
> > which are intended to be public but not used in tree to the
> > libxenguest.map:
> > - xc_cpuid_to_str
> > - xc_compression_add_page
> > - xc_compression_compress_pages
> > - xc_compression_create_context
> > - xc_compression_free_context
> > - xc_compression_reset_pagebuf
> > - xc_compression_uncompress_page
>
> These compression functions became unused when I dropped legacy
> migration.
Indeed, I anticipated them either coming back or getting removed at some
point.
> > diff --git a/tools/libxc/libxenctrl.map b/tools/libxc/libxenctrl.map
> > new file mode 100644
> > index 0000000..cc93a5b
> > --- /dev/null
> > +++ b/tools/libxc/libxenctrl.map
> > @@ -0,0 +1,18 @@
> > +{
> > + global:
> > + xc_*;
> > +
> > + /*
> > + * Supposedly internal functions which are also used
> > + * by libxenguest (only, it seems)
> > + */
> > + read_exact;
> > + write_exact;
> > + writev_exact;
>
> read/write_exact are used in libxc by xc_tmem.c, but only because the
> tmem part of legacy migration split across the two libraries.
They are also used by various osdep backend stuff in libxc, which should go
away with my split of those into other libraries and by xc_core.c (which is
in libxc, perhaps wrongly).
> In the long term, they should move to being xenguest private.
>
> ~Andrew
>
> > +
> > + /* Other un-namespaced functions used elsewhere in
> > tree */
> > + do_xen_hypercall;
> > + do_memory_op;
> > +
> > + local: *; /* Do not expose anything by default */
> > +};
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-07 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 13:51 [PATCH RFC] tools: add map files for libxen{store, ctrl, guest}.so Ian Campbell
2016-01-07 14:36 ` Andrew Cooper
2016-01-07 14:50 ` Ian Campbell [this message]
2016-01-07 14:49 ` Jan Beulich
2016-01-07 14:58 ` 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=1452178235.21055.222.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.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).