From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
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>, Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
xiakaixu <xiakaixu@huawei.com>,
Anne Mascarin <amascari@redhat.com>
Subject: Re: [PATCH 2/4] perf tools: allow user to specify hardware breakpoint bp_len
Date: Mon, 4 Aug 2014 14:27:51 -0500 [thread overview]
Message-ID: <53DFDEB7.1090307@amd.com> (raw)
In-Reply-To: <5391EC92.8040500@amd.com>
Frederic,
3.17 windows is now open. Do you think you could get this one in?
Thanks
Suravee
On 6/6/2014 11:30 AM, Suravee Suthikulanit wrote:
> This message has been archived. View the original item
> <http://ausev2.amd.com/EnterpriseVault/ViewMessage.asp?VaultId=1C7248B8A7CDE234D884C352F0CB2021B1110000amdvault.amd.com&SavesetId=201407115122720~201406061630160000~Z~F134EBF86540766B73DA6ADB45060FE1>
> On 6/3/2014 6:55 AM, Jiri Olsa wrote:
> > On Tue, Jun 03, 2014 at 10:36:22AM +0900, Namhyung Kim wrote:
> >> Hi Jiri,
> >>
> >> On Fri, 30 May 2014 15:39:06 +0200, Jiri Olsa wrote:
> >>> On Thu, May 29, 2014 at 05:26:51PM +0200, Frederic Weisbecker wrote:
> >>>> From: Jacob Shin <jacob.w.shin@gmail.com>
> >>>>
> >>>> Currently bp_len is given a default value of 4. Allow user to
> override it:
> >>>>
> >>>> $ perf stat -e mem:0x1000/8
> >>>> ^
> >>>> bp_len
> >>>>
> >>>> If no value is given, it will default to 4 as it did before.
> >>>
> >>> Namhyung,
> >>> both perf tols patches from this patchset mess up with hists
> >>> tests.. I havent found any connection yet.. any idea? ;-)
> >>
> >> So you already found the problem in the hpp->elide change and that's the
> >> reason of the failure, right? :)
> >
> > I haven't got a chance to test it yet.. but it looks like
> > thats the case.. I'll retest soon ;-)
> >
> > jirka
> >
> Anything I can do to help here?
>
> Thanks,
>
> Suravee
>
next prev parent reply other threads:[~2014-08-04 19:28 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 [this message]
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
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 2/4] perf tools: allow user to specify hardware breakpoint bp_len Frederic Weisbecker
2014-10-01 21:37 [GIT PULL] hw_breakpoints: Support AMD range breakpoints Frederic Weisbecker
2014-10-01 21:37 ` [PATCH 2/4] perf tools: allow user to specify hardware breakpoint bp_len Frederic Weisbecker
2014-09-24 13:45 [PATCH 0/4] perf: Support AMD range breakpoints v2 Frederic Weisbecker
2014-09-24 13:45 ` [PATCH 2/4] perf tools: allow user to specify hardware breakpoint bp_len 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 2/4] perf tools: allow user to specify hardware breakpoint bp_len 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=53DFDEB7.1090307@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=acme@ghostprotocols.net \
--cc=amascari@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jacob.w.shin@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--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.