From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Mackerras <paulus@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] perf_counter: powerpc: Add callchain support
Date: Sat, 27 Jun 2009 10:34:44 +0200 [thread overview]
Message-ID: <1246091684.31755.210.camel@twins> (raw)
In-Reply-To: <19013.44722.893263.275594@cargo.ozlabs.ibm.com>
On Sat, 2009-06-27 at 15:31 +1000, Paul Mackerras wrote:
> + if (regs) {
> + if (current_is_64bit())
> + perf_callchain_user_64(regs, entry);
> + else
> + perf_callchain_user_32(regs, entry);
> + }
Ingo do we need 32 on 64 stuff like that too?
next prev parent reply other threads:[~2009-06-27 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 5:30 [PATCH 1/2] powerpc: Allow perf_counters to access user memory at interrupt time Paul Mackerras
2009-06-27 5:31 ` [PATCH 2/2] perf_counter: powerpc: Add callchain support Paul Mackerras
2009-06-27 8:34 ` Peter Zijlstra [this message]
2009-06-27 16:58 ` Ingo Molnar
2009-07-23 6:38 ` [PATCH 1/2] powerpc: Allow perf_counters to access user memory at interrupt time Benjamin Herrenschmidt
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=1246091684.31755.210.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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).