Re: [PATCH v8 00/14] Add support for remote unwind

2016-06-02 Thread Jiri Olsa
On Thu, Jun 02, 2016 at 09:55:12AM +, He Kuang wrote: SNIP > and now we can use LIBUNWIND_DIR to specific custom dirctories > containing libunwind libs. > > v8: > > - Put unwind__register_ops call into unwind__prepare_access from >patch 4 to patch 3. > - Fail thread__insert_map on

Re: [PATCH v8 00/14] Add support for remote unwind

2016-06-02 Thread Jiri Olsa
On Thu, Jun 02, 2016 at 09:55:12AM +, He Kuang wrote: SNIP > and now we can use LIBUNWIND_DIR to specific custom dirctories > containing libunwind libs. > > v8: > > - Put unwind__register_ops call into unwind__prepare_access from >patch 4 to patch 3. > - Fail thread__insert_map on

[PATCH v8 00/14] Add support for remote unwind

2016-06-02 Thread He Kuang
v7 url: http://thread.gmane.org/gmane.linux.kernel/2231229/focus=2232166 Currently, perf script uses host unwind methods(local unwind) to parse perf.data callchain info regardless of the target architecture. So we get wrong result and no promotion when do remote unwind on other

[PATCH v8 00/14] Add support for remote unwind

2016-06-02 Thread He Kuang
v7 url: http://thread.gmane.org/gmane.linux.kernel/2231229/focus=2232166 Currently, perf script uses host unwind methods(local unwind) to parse perf.data callchain info regardless of the target architecture. So we get wrong result and no promotion when do remote unwind on other