From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: He Kuang <hekuang@huawei.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 00/14] Add support for remote unwind
Date: Fri, 3 Jun 2016 18:06:02 -0300 [thread overview]
Message-ID: <20160603210602.GA3095@kernel.org> (raw)
In-Reply-To: <20160603194205.GB27920@kernel.org>
Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu:
> > On Fri, Jun 03, 2016 at 03:33:09AM +0000, He Kuang wrote:
> > > v9:
> > > - Change function unwind__register_ops() to static.
> > > - Move up unwind__prepare_access() in thread__insert_map() and save
> > > map_groups__remove() call.
> > > - Enclose multiple line if/else into braces.
> > > - Fix miss modified function declaration for unwind__prepare_access()
> > > in patch 10.
>
> > for patchset:
>
> > Acked-by: Jiri Olsa <jolsa@kernel.org>
>
> Thanks, applied, build testing.
Build tested went ok, but then 'perf top' crashes:
[root@jouet ~]# perf top
perf: Segmentation fault
-------- backtrace --------
perf[0x55591b]
/lib64/libc.so.6(+0x34ab0)[0x7f38ad9c1ab0]
perf(normalize_arch+0x27)[0x534797]
perf(unwind__prepare_access+0xbb)[0x52b15b]
perf(thread__insert_map+0x27)[0x4d4837]
perf(machine__process_mmap2_event+0xd7)[0x4ca187]
perf(perf_event__synthesize_mmap_events+0x3e2)[0x491b32]
perf(perf_event__synthesize_threads+0x445)[0x492635]
perf(cmd_top+0xee0)[0x442f50]
perf[0x486a91]
perf(main+0x6ee)[0x42485e]
/lib64/libc.so.6(__libc_start_main+0xf0)[0x7f38ad9ad580]
perf(_start+0x29)[0x424949]
[0x0]
[root@jouet ~]#
And I bet that 'perf trace' will too, lemme see, well, it crashes even
more spetacularly, but that is the topic of another bug report, will
send soon.
Anyway, please try your patchkit with 'perf top' and 'perf trace', as
both don't use perf.data files, i.e. they work 'live', so probably
things that you touch in normalize_arch() are not initialized and need
to be setup.
- Arnaldo
next prev parent reply other threads:[~2016-06-03 21:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 3:33 [PATCH v9 00/14] Add support for remote unwind He Kuang
2016-06-03 3:33 ` [PATCH v9 01/14] perf tools: Use LIBUNWIND_DIR for remote libunwind feature check He Kuang
2016-06-08 8:45 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 02/14] perf tools: Decouple thread->address_space on libunwind He Kuang
2016-06-08 8:46 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 03/14] perf tools: Introducing struct unwind_libunwind_ops for local unwind He Kuang
2016-06-08 8:46 ` [tip:perf/core] perf unwind: Introduce 'struct unwind_libunwind_ops' " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 04/14] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map He Kuang
2016-06-08 8:47 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 05/14] perf tools: Don't mix LIBUNWIND_LIBS into LIBUNWIND_LDFLAGS He Kuang
2016-06-08 8:47 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 06/14] perf tools: Separate local/remote libunwind config He Kuang
2016-06-08 8:47 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 07/14] perf tools: Rename unwind-libunwind.c to unwind-libunwind-local.c He Kuang
2016-06-08 8:48 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 08/14] perf tools: Extract common API out of unwind-libunwind-local.c He Kuang
2016-06-08 8:48 ` [tip:perf/core] " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 09/14] perf tools: Export normalize_arch() function He Kuang
2016-06-08 8:49 ` [tip:perf/core] " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 10/14] perf tools: Check the target platform before assigning unwind methods He Kuang
2016-06-04 5:36 ` [PATCH v9 10/14 UPDATE] " He Kuang
2016-06-07 18:06 ` Arnaldo Carvalho de Melo
2016-06-08 8:49 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 11/14] perf tools: Change fixed name of libunwind__arch_reg_id to macro He Kuang
2016-06-08 8:50 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 12/14] perf tools: Introduce flag to separate local/remote unwind compilation He Kuang
2016-06-08 8:50 ` [tip:perf/core] perf unwind: " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 13/14] perf callchain: Support x86 target platform He Kuang
2016-06-08 8:51 ` [tip:perf/core] " tip-bot for He Kuang
2016-06-03 3:33 ` [PATCH v9 14/14] perf callchain: Support aarch64 cross-platform He Kuang
2016-06-08 8:51 ` [tip:perf/core] " tip-bot for He Kuang
2016-06-03 7:06 ` [PATCH v9 00/14] Add support for remote unwind Jiri Olsa
2016-06-03 19:42 ` Arnaldo Carvalho de Melo
2016-06-03 21:06 ` Arnaldo Carvalho de Melo [this message]
2016-06-03 21:09 ` Arnaldo Carvalho de Melo
2016-06-04 5:39 ` Hekuang
2016-06-07 15:12 ` Arnaldo Carvalho de Melo
2016-06-07 15:14 ` Arnaldo Carvalho de Melo
2016-06-07 19:44 ` Arnaldo Carvalho de Melo
2016-06-08 7:33 ` Hekuang
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=20160603210602.GA3095@kernel.org \
--to=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=hekuang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox