From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Pekka Enberg <penberg@kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: [PATCH/RFC 0/4] perf ui/gtk: Separate out GTK code to a shared object (v2)
Date: Tue, 6 Aug 2013 14:14:12 +0900 [thread overview]
Message-ID: <1375766056-19377-1-git-send-email-namhyung@kernel.org> (raw)
Hi,
This is v2 of gtk code separation patchset to reduce library
dependencies of the perf executable.
I only built libperf-gtk.so with -fPIC, and it's not linked to libperf
at build time. All unresolved symbols used for perf should be
resolved at runtime via perf executable (so libperf.a) - I didn't know
that the linker permits unresolved symbols in a shared library at
build time.
Tested on my x86-64 machine only. It seems work well for me.
The patch 1 is a bug fix and can be applied independently.
You can find it on my 'perf/separate-v2' branch in my tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Any comments are welcome, thanks
Namhyung
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>
Namhyung Kim (4):
perf ui/gtk: Fix segmentation fault on perf_hpp__for_each_format loop
perf tools: Separate out GTK codes to libperf-gtk.so
perf tools: Setup GTK browser dynamically
perf tools: Run dynamic loaded GTK browser
tools/perf/Makefile | 39 +++++++++++++++++++++++----------
tools/perf/builtin-annotate.c | 26 +++++++++++++++++++---
tools/perf/builtin-report.c | 16 ++++++++++++--
tools/perf/config/Makefile | 12 +++++++---
tools/perf/ui/gtk/annotate.c | 13 ++++++++---
tools/perf/ui/gtk/gtk.h | 16 ++++++++++++++
tools/perf/ui/gtk/hists.c | 2 --
tools/perf/ui/setup.c | 51 +++++++++++++++++++++++++++++++++++++++++--
tools/perf/ui/ui.h | 12 +---------
tools/perf/util/annotate.h | 24 --------------------
tools/perf/util/hist.h | 15 -------------
11 files changed, 150 insertions(+), 76 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-08-06 5:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 5:14 Namhyung Kim [this message]
2013-08-06 5:14 ` [PATCH 1/4] perf ui/gtk: Fix segmentation fault on perf_hpp__for_each_format loop Namhyung Kim
2013-08-06 5:56 ` Pekka Enberg
2013-08-12 10:23 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-08-06 5:14 ` [PATCH 2/4] perf tools: Separate out GTK codes to libperf-gtk.so Namhyung Kim
2013-08-06 5:56 ` Pekka Enberg
2013-08-06 5:14 ` [PATCH 3/4] perf tools: Setup GTK browser dynamically Namhyung Kim
2013-08-06 5:57 ` Pekka Enberg
2013-08-06 5:14 ` [PATCH 4/4] perf tools: Run dynamic loaded GTK browser Namhyung Kim
2013-08-06 5:58 ` Pekka Enberg
2013-08-07 20:09 ` [PATCH/RFC 0/4] perf ui/gtk: Separate out GTK code to a shared object (v2) Arnaldo Carvalho de Melo
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=1375766056-19377-1-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.org \
--cc=penberg@kernel.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
all inboxes | Powered by JetHome®