From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Anton Blanchard <anton@samba.org>,
davem@davemloft.net, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, fweisbec@gmail.com,
Ingo Molnar <mingo@elte.hu>,
benh@kernel.crashing.org, penberg@cs.helsinki.fi,
vegard.nossum@gmail.com, paulus@samba.org, williams@redhat.com,
acme@redhat.com
Subject: Re: [PATCH] basic perf support for sparc
Date: Sat, 1 Aug 2009 15:22:16 -0300 [thread overview]
Message-ID: <20090801182216.GA25334@ghostprotocols.net> (raw)
In-Reply-To: <20090801082048.GX12579@kernel.dk>
Em Sat, Aug 01, 2009 at 10:20:48AM +0200, Jens Axboe escreveu:
> On Sat, Aug 01 2009, Anton Blanchard wrote:
> >
> > Hi,
> >
> > > > Building the perf tool is somewhat involved on sparc64
> > > > though, since 64-bit versions of zlib/libelf/bfd aren't
> > > > directly available (at least on debian 5.x). But once you
> > > > get there, it runs :-). Would it be easier/functional
> > > > to build 32-bit userland perf instead?
> > >
> > > Same is true on ppc64, btw. How are others handling this?
> >
> > The requirement for libz was removed, so up until recently we only needed
> > a 64bit version of elfutils which is easy to build.
> >
> > It looks like we now have a requirement on binutils which is considerably
> > more painful to build. One option is to make the bfd requirement optional, all
> > you lose would be the ability to see c++ demangled names I think.
>
> Right, binutils is the ugly one. I got a libbfd.so built for both ppc
> and sparc, but it wasn't just a make && make install job. Personally I
> could not care less about losing c++ demangled name support, so that
> approach sounds fine to me :-)
Exactly, for a huge number of developers not being able to see demangled
C++ is okay, so I agree on adding smarts to not demangle when
binutils-devel is not available.
I thought about extracting the demangling bits out of binutils, ran away
screaming. I also hoped elfutils would have that by now, but it doesn't.
- Arnaldo
next prev parent reply other threads:[~2009-08-01 18:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 11:25 [PATCH] basic perf support for sparc Jens Axboe
2009-07-29 19:28 ` Jens Axboe
2009-08-01 1:14 ` Anton Blanchard
2009-08-01 8:20 ` Jens Axboe
2009-08-01 18:22 ` Arnaldo Carvalho de Melo [this message]
2009-08-02 18:41 ` Ingo Molnar
2009-08-02 19:44 ` Kyle McMartin
2009-08-02 19:50 ` Ingo Molnar
2009-08-02 20:11 ` Kyle McMartin
2009-08-02 20:33 ` Ingo Molnar
2009-08-02 20:47 ` Arnaldo Carvalho de Melo
2009-08-03 1:54 ` Arnaldo Carvalho de Melo
2009-08-04 3:33 ` Kyle McMartin
2009-08-04 9:25 ` Ingo Molnar
2009-08-04 9:29 ` Peter Zijlstra
2009-08-04 13:02 ` David Miller
2009-08-04 10:32 ` Frederic Riss
2009-08-04 10:38 ` Peter Zijlstra
2009-08-04 11:23 ` Frederic Riss
2009-08-04 11:28 ` Ingo Molnar
2009-08-05 12:10 ` Peter Zijlstra
2009-08-05 12:21 ` Jens Axboe
2009-08-05 12:33 ` Ingo Molnar
2009-08-05 12:16 ` [tip:perfcounters/urgent] perf: Auto-detect libbfd tip-bot for Peter Zijlstra
2009-08-05 14:29 ` Peter Zijlstra
2009-08-05 18:58 ` Peter Zijlstra
2009-08-02 20:17 ` [PATCH] basic perf support for sparc David Miller
2009-08-02 20:25 ` Ingo Molnar
2009-08-06 7:02 ` Jens Axboe
2009-08-12 18:06 ` David Miller
2009-08-12 18:13 ` Jens Axboe
2009-08-17 1:31 ` David Miller
2009-08-17 6:48 ` Jens Axboe
2009-08-17 7:57 ` Ingo Molnar
2009-09-04 4:37 ` David Miller
2009-09-04 5:02 ` Ingo Molnar
2009-09-04 5:09 ` David Miller
2009-09-04 5:20 ` Jens Axboe
2009-09-04 6:34 ` Jens Axboe
2009-09-04 6:44 ` Ingo Molnar
2009-09-04 9:57 ` David Miller
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=20090801182216.GA25334@ghostprotocols.net \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
--cc=williams@redhat.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.