[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140925075516.GA14265@krava.brq.redhat.com>
Date: Thu, 25 Sep 2014 09:55:16 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Namhyung Kim <namhyung@...nel.org>,
Oleg Nesterov <oleg@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
xiakaixu <xiakaixu@...wei.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@....com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Jacob Shin <jacob.w.shin@...il.com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH 0/4] perf: Support AMD range breakpoints v2
On Wed, Sep 24, 2014 at 03:45:47PM +0200, Frederic Weisbecker wrote:
> I'm following up on this patchset.
> If that's ok for you I may do a pull request in a few days. I'll just
> need to make sure it doesn't break anything on the tooling side which I
> can't test right now due to some obscure build errors.
>
> Ah it would be nice if someone who knows well perf test and bison sides
> can check those particular bits.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> perf/core
>
> HEAD: 6dba1406bb46939ef42501450d6bfbd4e154280c
>
> 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
the tools changes looks ok:
Acked-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