All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hekuang <hekuang@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
	<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
	<wangnan0@huawei.com>, <jpoimboe@redhat.com>,
	<ak@linux.intel.com>, <eranian@google.com>, <namhyung@kernel.org>,
	<adrian.hunter@intel.com>, <sukadev@linux.vnet.ibm.com>,
	<masami.hiramatsu.pt@hitachi.com>, <tumanova@linux.vnet.ibm.com>,
	<kan.liang@intel.com>, <penberg@kernel.org>, <dsahern@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Fixes on remote unwind
Date: Tue, 21 Jun 2016 09:59:00 +0800	[thread overview]
Message-ID: <57689F64.4070309@huawei.com> (raw)
In-Reply-To: <1465380938-64371-1-git-send-email-hekuang@huawei.com>



在 2016/6/8 18:15, He Kuang 写道:
> The remote unwind can supported scenario where we collect on a x86_64
> machine and want to do analysis on a ARM64 or x86-32 machine. Though
> this is not tested, after Arnaldo questioned the above issue, I tested
> and found a bug.
>
> In util/unwind-libunwind-local.c, PERF_REG_SP/IP is used, but those
> macros are assigned to the host platform, we should redefine them in
> the wrapper file, for example in "util/libunwind/x86_32.c".
>
> After fixing this problem, i686 perf.data can be parsed on aarch64
> machine.
>
> To Arnaldo, I noticed that this patch
> "perf tools: Find vdso supporting cross-platform analysis"
> is not on "origin/perf/unwind" branch, this patch was applied, please
> check if it was missed, the above test needs this patch.
Thanks for solving this, and please have a look at the patches in
this thread.
>
> He Kuang (3):
>    perf unwind: Change macro names of perf register
>    perf unwind: Fix wrongly used regs for x86_32 unwind
>    perf unwind: Fix wrongly used regs for aarch64 unwind
>
>   tools/perf/util/libunwind/arm64.c        | 5 +++++
>   tools/perf/util/libunwind/x86_32.c       | 6 ++++++
>   tools/perf/util/unwind-libunwind-local.c | 6 ++++--
>   tools/perf/util/unwind.h                 | 9 +++++++++
>   4 files changed, 24 insertions(+), 2 deletions(-)
>

  parent reply	other threads:[~2016-06-21  2:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 10:15 [PATCH 0/3] Fixes on remote unwind He Kuang
2016-06-08 10:15 ` [PATCH 1/3] perf unwind: Change macro names of perf register He Kuang
2016-06-08 10:15 ` [PATCH 2/3] perf unwind: Fix wrongly used regs for x86_32 unwind He Kuang
2016-06-08 10:15 ` [PATCH 3/3] perf unwind: Fix wrongly used regs for aarch64 unwind He Kuang
2016-06-12 10:03 ` [PATCH 0/3] Fixes on remote unwind Hekuang
2016-06-21  1:59 ` Hekuang [this message]
2016-06-21  7:33 ` 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=57689F64.4070309@huawei.com \
    --to=hekuang@huawei.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=tumanova@linux.vnet.ibm.com \
    --cc=wangnan0@huawei.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.