From: Ian Munsie <imunsie@au1.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
LKML Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf top broken on ppc64
Date: Tue, 27 Apr 2010 11:30:21 +1000 [thread overview]
Message-ID: <1272331742-sup-1208@au1.ibm.com> (raw)
In-Reply-To: <12E39DE6-0957-43CD-8DD4-24970AAF45D3@suse.de>
> > I'm using 32 bit userland and 64 bit kernel on a PowerPC box and it's working for me.
> > Are you building perf from the tip tree?
>
> I'm using kvm.git which is pretty close to tip. The version says something 2.6.34-rc3'ish. Has anything significantly changed since then?
>
> Either way - I'll give it a try.
Hey Alex,
Did perf from the tip tree work for you?
Cheers,
-Ian
next prev parent reply other threads:[~2010-04-27 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 23:21 perf top broken on ppc64 Alexander Graf
2010-04-21 5:29 ` Ian Munsie
2010-04-21 9:29 ` Alexander Graf
2010-04-27 1:30 ` Ian Munsie [this message]
2010-04-27 7:39 ` Alexander Graf
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=1272331742-sup-1208@au1.ibm.com \
--to=imunsie@au1.ibm.com \
--cc=acme@redhat.com \
--cc=agraf@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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