From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v5 0/7] perf: Stream comparison
Date: Fri, 11 Sep 2020 09:43:37 +0800 [thread overview]
Message-ID: <ac5f770a-75f7-b4a7-bffe-6ff5bbad48c5@linux.intel.com> (raw)
In-Reply-To: <20200910092237.GE1627030@krava>
Hi Jiri,
On 9/10/2020 5:22 PM, Jiri Olsa wrote:
> On Mon, Sep 07, 2020 at 12:15:59PM +0800, Jin Yao wrote:
>
> SNIP
>
>> main div.c:39
>>
>> [ Hot streams in new perf data only ]
>>
>> hot chain 1:
>> cycles: 4, hits: 4.54%
>> --------------------------
>> main div.c:42
>> compute_flag div.c:28
>>
>> hot chain 2:
>> cycles: 5, hits: 3.51%
>> --------------------------
>> main div.c:39
>> main div.c:44
>> main div.c:42
>> compute_flag div.c:28
>>
>> v5:
>> ---
>> 1. Remove enum stream_type
>> 2. Rebase to perf/core
>
> hi,
> which commit did you base on? I can't apply on current perf/core
>
> thanks,
> jirka
>
Let me rebase the patchset again.
Thanks
Jin Yao
prev parent reply other threads:[~2020-09-11 1:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 4:15 [PATCH v5 0/7] perf: Stream comparison Jin Yao
2020-09-07 4:16 ` [PATCH v5 1/7] perf util: Create streams Jin Yao
2020-09-07 4:16 ` [PATCH v5 2/7] perf util: Get the evsel_streams by evsel_idx Jin Yao
2020-09-07 4:16 ` [PATCH v5 3/7] perf util: Compare two streams Jin Yao
2020-09-07 4:16 ` [PATCH v5 4/7] perf util: Link stream pair Jin Yao
2020-09-07 4:16 ` [PATCH v5 5/7] perf util: Calculate the sum of total streams hits Jin Yao
2020-09-07 4:16 ` [PATCH v5 6/7] perf util: Report hot streams Jin Yao
2020-09-07 4:16 ` [PATCH v5 7/7] perf diff: Support hot streams comparison Jin Yao
2020-09-10 9:22 ` [PATCH v5 0/7] perf: Stream comparison Jiri Olsa
2020-09-11 1:43 ` Jin, Yao [this message]
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=ac5f770a-75f7-b4a7-bffe-6ff5bbad48c5@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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