Re: [GIT PULL][RESEND] hw_breakpoints: Support AMD range breakpoints
From: Ingo Molnar
Date: Mon Dec 08 2014 - 05:53:44 EST
* Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
> Ingo,
>
> Please pull the perf/core-v3 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> perf/core-v3
>
> HEAD: 36748b9518a2437beffe861b47dff6d12b736b3f
>
> It has been acked by Jiri and Oleg.
> ---
> Summary:
>
> * Extend breakpoint tools and core to support address range through perf
> event with initial backend support for AMD extended breakpoints.
> Syntax is:
>
> perf record -e mem:addr/len:type
>
> For example set write breakpoint from 0x1000 to 0x1200 (0x1000 + 512)
>
> perf record -e mem:0x1000/512:w
>
> * Clean up a bit breakpoint code validation
> ---
>
>
> Thanks,
> Frederic
> ---
>
> Jacob Shin (4):
> perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8
> perf tools: allow user to specify hardware breakpoint bp_len
> perf tools: add hardware breakpoint bp_len test cases
> perf/x86: Remove get_hbp_len and replace with bp_len
>
>
> arch/x86/include/asm/cpufeature.h | 2 ++
> arch/x86/include/asm/debugreg.h | 5 +++
> arch/x86/include/asm/hw_breakpoint.h | 1 +
> arch/x86/include/uapi/asm/msr-index.h | 4 +++
> arch/x86/kernel/cpu/amd.c | 19 +++++++++++
> arch/x86/kernel/hw_breakpoint.c | 45 ++++++++++---------------
> tools/perf/Documentation/perf-record.txt | 7 ++--
> tools/perf/tests/parse-events.c | 58 ++++++++++++++++++++++++++++++++
> tools/perf/util/parse-events.c | 21 ++++++------
> tools/perf/util/parse-events.h | 2 +-
> tools/perf/util/parse-events.l | 1 +
> tools/perf/util/parse-events.y | 26 ++++++++++++--
> 12 files changed, 148 insertions(+), 43 deletions(-)
Pulled into tip:perf/hw_breakpoints, thanks Frederic!
It might not make it into v3.19, we'll see.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/