public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	xiakaixu <xiakaixu@huawei.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Jacob Shin <jacob.w.shin@gmail.com>
Subject: Re: [GIT PULL][RESEND] hw_breakpoints: Support AMD range breakpoints
Date: Mon, 8 Dec 2014 11:53:33 +0100	[thread overview]
Message-ID: <20141208105333.GC22066@gmail.com> (raw)
In-Reply-To: <1417652025-2305-1-git-send-email-fweisbec@gmail.com>


* Frederic Weisbecker <fweisbec@gmail.com> 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

  parent reply	other threads:[~2014-12-08 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  0:13 [GIT PULL][RESEND] hw_breakpoints: Support AMD range breakpoints Frederic Weisbecker
2014-12-04  0:13 ` [PATCH 1/4] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8 Frederic Weisbecker
2014-12-04  0:13 ` [PATCH 2/4] perf tools: allow user to specify hardware breakpoint bp_len Frederic Weisbecker
2014-12-04  0:13 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases Frederic Weisbecker
2014-12-04  0:13 ` [PATCH 4/4] perf/x86: Remove get_hbp_len and replace with bp_len Frederic Weisbecker
2014-12-08 10:53 ` Ingo Molnar [this message]
2014-12-08 15:50   ` [GIT PULL][RESEND] hw_breakpoints: Support AMD range breakpoints Frederic Weisbecker

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=20141208105333.GC22066@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=jacob.w.shin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xiakaixu@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