From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: irogers@google.com, peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
adrian.hunter@intel.com, ak@linux.intel.com, eranian@google.com
Subject: Re: [PATCH V2 0/9] Support branch counters in block annotation
Date: Tue, 13 Aug 2024 11:15:49 -0400 [thread overview]
Message-ID: <bdf150ed-6a41-4c54-a754-13c1f194fac3@linux.intel.com> (raw)
In-Reply-To: <Zrps-_ajW_zfze66@x1>
On 2024-08-12 4:13 p.m., Arnaldo Carvalho de Melo wrote:
> On Mon, Aug 12, 2024 at 12:39:17PM -0700, Namhyung Kim wrote:
>> On Thu, Aug 08, 2024 at 12:33:15PM -0700, kan.liang@linux.intel.com wrote:
>>> From: Kan Liang <kan.liang@linux.intel.com>
>>> Kan Liang (9):
>>> perf report: Fix --total-cycles --stdio output error
>>> perf report: Remove the first overflow check for branch counters
>>> perf evlist: Save branch counters information
>>> perf annotate: Save branch counters for each block
>>> perf evsel: Assign abbr name for the branch counter events
>>> perf report: Display the branch counter histogram
>>> perf annotate: Display the branch counter histogram
>>> perf script: Add branch counters
>>> perf test: Add new test cases for the branch counter feature
>>
>> Acked-by: Namhyung Kim <namhyung@kernel.org>
>
> Clashed with something here, can you please take a look and rebase to
> what is in perf-tools-next/perf-tools-next?
Tools-next/perf-tools-next doesn't include Weilin's TPEBS patch. So I
fail at the patch 5, rather than patch 6 (the failure you observed.)
Can you please update the perf-tools-next?
Or should I re-base on top of the tmp.perf-tools-next?
$ git branch -v
master 1639fae5132b Merge tag 'drm-fixes-2023-06-17' of
git://anongit.freedesktop.org/drm/drm
* perf-tools-next cb1898f58e0f perf annotate-data: Support
--skip-empty option
tmp.perf-tools-next 9da782071202 perf test: Add test for Intel TPEBS
counting mode
$ git branch --show-current
perf-tools-next
$ git am lbr_event_logging_v2/000*
Applying: perf report: Fix --total-cycles --stdio output error
Applying: perf report: Remove the first overflow check for branch counters
Applying: perf evlist: Save branch counters information
Applying: perf annotate: Save branch counters for each block
Applying: perf evsel: Assign abbr name for the branch counter events
error: patch failed: tools/perf/util/evlist.c:33
error: tools/perf/util/evlist.c: patch does not apply
Patch failed at 0005 perf evsel: Assign abbr name for the branch counter
events
Thanks,
Kan
>
> - Arnaldo
>
> ✓ [PATCH v2 9/9] perf test: Add new test cases for the branch counter feature
> + Acked-by: Namhyung Kim <namhyung@kernel.org> (✓ DKIM/kernel.org)
> + Reviewed-by: Andi Kleen <ak@linux.intel.com> (✓ DKIM/intel.com)
> + Link: https://lore.kernel.org/r/20240808193324.2027665-10-kan.liang@linux.intel.com
> + Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> ---
> ✓ Signed: DKIM/intel.com (From: kan.liang@linux.intel.com)
> ---
> Total patches: 9
> ---
> Cover: ./v2_20240808_kan_liang_support_branch_counters_in_block_annotation.cover
> Link: https://lore.kernel.org/r/20240808193324.2027665-1-kan.liang@linux.intel.com
> Base: not specified
> git am ./v2_20240808_kan_liang_support_branch_counters_in_block_annotation.mbx
> ⬢[acme@toolbox perf-tools-next]$ git am ./v2_20240808_kan_liang_support_branch_counters_in_block_annotation.mbx
> Applying: perf report: Fix --total-cycles --stdio output error
> Applying: perf report: Remove the first overflow check for branch counters
> Applying: perf evlist: Save branch counters information
> Applying: perf annotate: Save branch counters for each block
> Applying: perf evsel: Assign abbr name for the branch counter events
> Applying: perf report: Display the branch counter histogram
> error: patch failed: tools/perf/util/annotate.h:551
> error: tools/perf/util/annotate.h: patch does not apply
> Patch failed at 0006 perf report: Display the branch counter histogram
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> ⬢[acme@toolbox perf-tools-next]$
next prev parent reply other threads:[~2024-08-13 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 19:33 [PATCH V2 0/9] Support branch counters in block annotation kan.liang
2024-08-08 19:33 ` [PATCH V2 1/9] perf report: Fix --total-cycles --stdio output error kan.liang
2024-08-08 19:33 ` [PATCH V2 2/9] perf report: Remove the first overflow check for branch counters kan.liang
2024-08-08 19:33 ` [PATCH V2 3/9] perf evlist: Save branch counters information kan.liang
2024-08-08 19:33 ` [PATCH V2 4/9] perf annotate: Save branch counters for each block kan.liang
2024-08-08 19:33 ` [PATCH V2 5/9] perf evsel: Assign abbr name for the branch counter events kan.liang
2024-08-08 19:33 ` [PATCH V2 6/9] perf report: Display the branch counter histogram kan.liang
2024-08-08 19:33 ` [PATCH V2 7/9] perf annotate: " kan.liang
2024-08-08 19:33 ` [PATCH V2 8/9] perf script: Add branch counters kan.liang
2024-08-08 19:33 ` [PATCH V2 9/9] perf test: Add new test cases for the branch counter feature kan.liang
2024-08-08 20:27 ` [PATCH V2 0/9] Support branch counters in block annotation Andi Kleen
2024-08-12 19:39 ` Namhyung Kim
2024-08-12 20:13 ` Arnaldo Carvalho de Melo
2024-08-13 15:15 ` Liang, Kan [this message]
2024-08-13 15:17 ` Arnaldo Carvalho de Melo
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=bdf150ed-6a41-4c54-a754-13c1f194fac3@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).