Re: [PATCH v6 03/11] perf tools: Introducing struct unwind_libunwind_ops for local unwind

On Sat, May 28, 2016 at 11:59:52AM +, He Kuang wrote: > Currently, libunwind operations are fixed, and they are chosen > according to the host architecture. This will lead a problem that if a > thread is run as x86_32 on x86_64 machine, perf will use libunwind > methods for x86_64 to parse the

Re: [PATCH v6 03/11] perf tools: Introducing struct unwind_libunwind_ops for local unwind

On Sat, May 28, 2016 at 11:59:52AM +, He Kuang wrote: > Currently, libunwind operations are fixed, and they are chosen > according to the host architecture. This will lead a problem that if a > thread is run as x86_32 on x86_64 machine, perf will use libunwind > methods for x86_64 to parse the

[PATCH v6 03/11] perf tools: Introducing struct unwind_libunwind_ops for local unwind

Currently, libunwind operations are fixed, and they are chosen according to the host architecture. This will lead a problem that if a thread is run as x86_32 on x86_64 machine, perf will use libunwind methods for x86_64 to parse the callchain and get wrong result. This patch changes the fixed

[PATCH v6 03/11] perf tools: Introducing struct unwind_libunwind_ops for local unwind

Currently, libunwind operations are fixed, and they are chosen according to the host architecture. This will lead a problem that if a thread is run as x86_32 on x86_64 machine, perf will use libunwind methods for x86_64 to parse the callchain and get wrong result. This patch changes the fixed