[tip:perf/core] perf probe: Fix to copy the type for raw parameters
in [Kernel]
|
Prev: [PATCH 12/14] staging: comedi (adv_pci1723): use PCI_DEVICE() macro
Next: [tip:perf/core] perf tui: Introduce list_head based generic ui_browser refresh routine
From: tip-bot for Masami Hiramatsu on 7 Aug 2010 03:10 Commit-ID: 58432e1f3625ef22b347ec8f9487e1852aa9ad67 Gitweb: http://git.kernel.org/tip/58432e1f3625ef22b347ec8f9487e1852aa9ad67 Author: Masami Hiramatsu <masami.hiramatsu.pt(a)hitachi.com> AuthorDate: Tue, 3 Aug 2010 11:11:36 +0900 Committer: Arnaldo Carvalho de Melo <acme(a)redhat.com> CommitDate: Fri, 6 Aug 2010 16:25:56 -0300 perf probe: Fix to copy the type for raw parameters Copy type field if it is for raw parameters. Without this fix, perf probe drops the type if user passes it for raw parameters (e.g. %ax:u32 will be converted to %ax). Cc: Peter Zijlstra <a.p.zijlstra(a)chello.nl> Cc: Paul Mackerras <paulus(a)samba.org> Cc: Ingo Molnar <mingo(a)elte.hu> Cc: Frederic Weisbecker <fweisbec(a)gmail.com> Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt(a)hitachi.com> LKML-Reference: <4C577AD8.50808(a)hitachi.com> Signed-off-by: Arnaldo Carvalho de Melo <acme(a)redhat.com> --- tools/perf/util/probe-finder.c | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/tools/perf/util/probe-finder.c b/tools/perf/util/probe-finder.c index 6c7750d..5251366 100644 --- a/tools/perf/util/probe-finder.c +++ b/tools/perf/util/probe-finder.c @@ -705,8 +705,12 @@ static int find_variable(Dwarf_Die *sp_die, struct probe_finder *pf) pf->tvar->value = strdup(pf->pvar->var); if (pf->tvar->value == NULL) return -ENOMEM; - else - return 0; + if (pf->pvar->type) { + pf->tvar->type = strdup(pf->pvar->type); + if (pf->tvar->type == NULL) + return -ENOMEM; + } + return 0; } pr_debug("Searching '%s' variable in context.\n", -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |