[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141211222145.GE26788@krava.redhat.com>
Date: Thu, 11 Dec 2014 23:21:45 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: kan.liang@...el.com
Cc: acme@...nel.org, a.p.zijlstra@...llo.nl, eranian@...gle.com,
linux-kernel@...r.kernel.org, mingo@...hat.com, paulus@...ba.org,
ak@...ux.intel.com, namhyung@...nel.org
Subject: Re: [PATCH V5 0/3] perf tool: Haswell LBR call stack support (user)
On Tue, Dec 02, 2014 at 10:06:51AM -0500, kan.liang@...el.com wrote:
SNIP
>
> Please find the kernel part patch at https://lkml.org/lkml/2014/11/6/432
>
> Changes since v1
> - Update help document
> - Force exclude_user to 0 with warning in LBR call stack
> - Dump both lbr and fp info when report -D
> - Reconstruct thread__resolve_callchain_sample and split it into two patches
> - Use has_branch_callstack function to check LBR call stack available
>
> Changes since v2
> - Rebase to 025ce5d33373
>
> Changes since v3
> - Rebase to cc502c23aadf
> - Separated function for lbr call stack sample resolve and print
> - Some minor changes according to comments
>
> Changes since V4
> - Rebase to 09a6a1b
> - Falling back to framepointers if LBR not available, and warning user
>
> Kan Liang (3):
> perf tools: enable LBR call stack support
> perf tool: Move cpumode resolve code to add_callchain_ip
> perf tools: Construct LBR call chain
haven't reviewed the kernel part, but the user part
seems to work properly..
Tested-by: Jiri Olsa <jolsa@...nel.org>
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists