From: Jiri Olsa <jolsa@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.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>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 0/4] perf: Support AMD range breakpoints v2
Date: Thu, 25 Sep 2014 09:55:16 +0200 [thread overview]
Message-ID: <20140925075516.GA14265@krava.brq.redhat.com> (raw)
In-Reply-To: <1411566351-10987-1-git-send-email-fweisbec@gmail.com>
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@kernel.org>
jirka
next prev parent reply other threads:[~2014-09-25 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 13:45 [PATCH 0/4] perf: Support AMD range breakpoints v2 Frederic Weisbecker
2014-09-24 13:45 ` [PATCH 1/4] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8 Frederic Weisbecker
2014-09-24 13:45 ` [PATCH 2/4] perf tools: allow user to specify hardware breakpoint bp_len Frederic Weisbecker
2014-09-24 13:45 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases Frederic Weisbecker
2014-09-24 13:45 ` [PATCH 4/4] perf/x86: Remove get_hbp_len and replace with bp_len Frederic Weisbecker
2014-09-25 7:55 ` Jiri Olsa [this message]
2014-09-26 15:04 ` [PATCH 0/4] perf: Support AMD range breakpoints v2 Oleg Nesterov
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=20140925075516.GA14265@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=jacob.w.shin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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