From: Frederic Weisbecker <fweisbec@gmail.com>
To: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jacob Shin <jacob.w.shin@gmail.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
xiakaixu <xiakaixu@huawei.com>
Subject: Re: [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases
Date: Fri, 30 May 2014 17:24:25 +0200 [thread overview]
Message-ID: <20140530152423.GD25555@localhost.localdomain> (raw)
In-Reply-To: <53889A75.7060105@amd.com>
On Fri, May 30, 2014 at 09:49:25AM -0500, Suravee Suthikulanit wrote:
> On 5/29/2014 10:26 AM, Frederic Weisbecker wrote:
> >@@ -1389,6 +1432,21 @@ static struct evlist_test test__events[] = {
> > .check = test__pinned_group,
> > .id = 41,
> > },
> >+ {
> >+ .name = "mem:0/1",
> >+ .check = test__checkevent_breakpoint_len,
> >+ .id = 42,
> >+ },
> >+ {
> >+ .name = "mem:0/2:w",
> >+ .check = test__checkevent_breakpoint_len_w,
> >+ .id = 43,
> >+ },
> >+ {
> >+ .name = "mem:0/4:rw:u",
> >+ .check = test__checkevent_breakpoint_len_rw_modifier,
> >+ .id = 44
> >+ },
> > #if defined(__s390x__)
> > {
> > .name = "kvm-s390:kvm_s390_create_vm",
> Frederic,
>
> This hunk seems to fail to apply on the main tree. Which tree are
> you working on?
I forgot to say it's rebased on top of:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf/core
> Suravee
>
next prev parent reply other threads:[~2014-05-30 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 15:26 [PATCH 0/4] perf: Support AMD range breakpoints Frederic Weisbecker
2014-05-29 15:26 ` [PATCH 1/4] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8 Frederic Weisbecker
2014-05-30 13:33 ` Frederic Weisbecker
2014-05-31 1:55 ` Suravee Suthikulpanit
2014-06-03 15:37 ` Frederic Weisbecker
2014-05-29 15:26 ` [PATCH 2/4] perf tools: allow user to specify hardware breakpoint bp_len Frederic Weisbecker
2014-05-30 13:39 ` Jiri Olsa
2014-06-03 1:36 ` Namhyung Kim
2014-06-03 11:55 ` Jiri Olsa
2014-06-06 16:30 ` Suravee Suthikulanit
2014-08-04 19:27 ` Suravee Suthikulanit
2014-05-29 15:26 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases Frederic Weisbecker
2014-05-30 14:49 ` Suravee Suthikulanit
2014-05-30 15:24 ` Frederic Weisbecker [this message]
2014-05-29 15:26 ` [PATCH 4/4] perf/x86: Remove get_hbp_len and replace with bp_len Frederic Weisbecker
2014-05-30 13:06 ` [PATCH 0/4] perf: Support AMD range breakpoints Jiri Olsa
2014-06-01 18:06 ` Suravee Suthikulpanit
-- strict thread matches above, loose matches on Subject: below --
2014-12-04 0:13 [GIT PULL][RESEND] hw_breakpoints: " Frederic Weisbecker
2014-12-04 0:13 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases Frederic Weisbecker
2014-10-01 21:37 [GIT PULL] hw_breakpoints: Support AMD range breakpoints Frederic Weisbecker
2014-10-01 21:37 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases Frederic Weisbecker
2014-09-24 13:45 [PATCH 0/4] perf: Support AMD range breakpoints v2 Frederic Weisbecker
2014-09-24 13:45 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases Frederic Weisbecker
2013-12-11 12:28 [PATCH V6 0/4] perf/x86/amd: AMD Family 16h Data Breakpoint Extensions suravee.suthikulpanit
2013-12-11 12:28 ` [PATCH 3/4] perf tools: add hardware breakpoint bp_len test cases suravee.suthikulpanit
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=20140530152423.GD25555@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=jacob.w.shin@gmail.com \
--cc=jolsa@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.