From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@intel.com
Cc: acme@kernel.org, a.p.zijlstra@chello.nl, eranian@google.com,
linux-kernel@vger.kernel.org, mingo@redhat.com, paulus@samba.org,
ak@linux.intel.com
Subject: Re: [PATCH V3 2/3] perf tool: Move cpumode resolve code to add_callchain_ip
Date: Mon, 17 Nov 2014 14:57:57 +0100 [thread overview]
Message-ID: <20141117135757.GA21532@krava.brq.redhat.com> (raw)
In-Reply-To: <1415972652-17310-3-git-send-email-kan.liang@intel.com>
On Fri, Nov 14, 2014 at 08:44:11AM -0500, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
SNIP
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1384,11 +1384,35 @@ struct mem_info *sample__resolve_mem(struct perf_sample *sample,
> static int add_callchain_ip(struct thread *thread,
> struct symbol **parent,
> struct addr_location *root_al,
> - int cpumode,
> + u8 cpumode,
> u64 ip)
> {
> struct addr_location al;
>
> + if (ip >= PERF_CONTEXT_MAX) {
> + switch (ip) {
> + case PERF_CONTEXT_HV:
> + cpumode = PERF_RECORD_MISC_HYPERVISOR;
> + break;
> + case PERF_CONTEXT_KERNEL:
> + cpumode = PERF_RECORD_MISC_KERNEL;
> + break;
> + case PERF_CONTEXT_USER:
> + cpumode = PERF_RECORD_MISC_USER;
> + break;
> + default:
> + pr_debug("invalid callchain context: "
> + "%"PRId64"\n", (s64) ip);
> + /*
> + * It seems the callchain is corrupted.
> + * Discard all.
> + */
> + callchain_cursor_reset(&callchain_cursor);
> + return 1;
> + }
> + return 0;
extra whitespace ^^^^^^^
> + }
> +
> al.filtered = 0;
> al.sym = NULL;
> thread__find_addr_location(thread, cpumode, MAP__FUNCTION,
SNIP
> - * Discard all.
> - */
> - callchain_cursor_reset(&callchain_cursor);
> - return 0;
> - }
> - continue;
> - }
> -
> err = add_callchain_ip(thread, parent, root_al,
> cpumode, ip);
hm, why do we need to pass cpumode in here? it should be handled within
add_callchain_ip in add_callchain_ip function, right?
jirka
next prev parent reply other threads:[~2014-11-17 13:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 13:44 [PATCH V3 0/3] perf tool: Haswell LBR call stack support (user) kan.liang
2014-11-14 13:44 ` [PATCH V3 1/3] perf tools: enable LBR call stack support kan.liang
2014-11-18 5:54 ` Namhyung Kim
2014-11-18 13:57 ` Liang, Kan
2014-11-14 13:44 ` [PATCH V3 2/3] perf tool: Move cpumode resolve code to add_callchain_ip kan.liang
2014-11-17 13:57 ` Jiri Olsa [this message]
2014-11-17 14:00 ` Jiri Olsa
2014-11-18 8:24 ` Jiri Olsa
2014-11-21 15:06 ` Liang, Kan
2014-11-21 15:19 ` Arnaldo Carvalho de Melo
2014-11-14 13:44 ` [PATCH V3 3/3] perf tools: Construct LBR call chain kan.liang
2014-11-17 15:54 ` Jiri Olsa
2014-11-17 17:41 ` Liang, Kan
2014-11-18 6:13 ` Namhyung Kim
2014-11-18 7:55 ` Jiri Olsa
2014-11-18 14:37 ` Liang, Kan
2014-11-18 19:40 ` Liang, Kan
2014-11-19 5:57 ` Namhyung Kim
2014-11-17 15:55 ` Jiri Olsa
2014-11-18 6:14 ` Namhyung Kim
2014-11-18 6:25 ` Namhyung Kim
2014-11-18 14:01 ` Liang, Kan
2014-11-19 6:01 ` Namhyung Kim
2014-11-19 13:37 ` Liang, Kan
2014-11-17 16:01 ` [PATCH V3 0/3] perf tool: Haswell LBR call stack support (user) Jiri Olsa
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=20141117135757.GA21532@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
Powered by JetHome