From: Jiri Olsa <jolsa@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.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 v2 4/7] perf diff: Use hists to manage basic blocks per symbol
Date: Tue, 11 Jun 2019 10:56:06 +0200 [thread overview]
Message-ID: <20190611085606.GA11510@krava> (raw)
In-Reply-To: <4bbc5085-c8b0-5e36-419c-6ee754186027@linux.intel.com>
On Sat, Jun 08, 2019 at 07:41:47PM +0800, Jin, Yao wrote:
>
>
> On 6/5/2019 7:44 PM, Jiri Olsa wrote:
> > On Mon, Jun 03, 2019 at 10:36:14PM +0800, Jin Yao wrote:
> >
> > SNIP
> >
> > > diff --git a/tools/perf/util/sort.h b/tools/perf/util/sort.h
> > > index 43623fa..d1641da 100644
> > > --- a/tools/perf/util/sort.h
> > > +++ b/tools/perf/util/sort.h
> > > @@ -79,6 +79,9 @@ struct hist_entry_diff {
> > > /* HISTC_WEIGHTED_DIFF */
> > > s64 wdiff;
> > > +
> > > + /* PERF_HPP_DIFF__CYCLES */
> > > + s64 cycles;
> > > };
> > > };
> > > @@ -143,6 +146,9 @@ struct hist_entry {
> > > struct branch_info *branch_info;
> > > long time;
> > > struct hists *hists;
> > > + void *block_hists;
> > > + int block_idx;
> > > + int block_num;
> > > struct mem_info *mem_info;
> > > struct block_info *block_info;
> >
> > could you please not add the new block* stuff in here,
> > and instead use the "c2c model" and use yourr own struct
> > on top of hist_entry? we are trying to librarize this
> > stuff and keep only necessary things in here..
> >
> > you're already using hist_entry_ops, so should be easy
> >
> > something like:
> >
> > struct block_hist_entry {
> > void *block_hists;
> > int block_idx;
> > int block_num;
> > struct block_info *block_info;
> >
> > struct hist_entry he;
> > };
> >
> >
> >
> > jirka
> >
>
> Hi Jiri,
>
> After more considerations, maybe I can't move these stuffs from hist_entry
> to block_hist_entry.
why?
>
> Actually we use 2 kinds of hist_entry in this patch series. On kind of
> hist_entry is for symbol/function. The other kind of hist_entry is for basic
> block.
correct
so the way I see it the processing goes like this:
1) there's standard hist_entry processing ending up
with evsel->hists->rb_root full of hist entries
2) then you process every hist_entry and create
new 'struct hists' for each and fill it with
symbol counts data
you could add 'struct hist_entry_ops' for the 1) processing
that adds the 'struct hists' object for each hist_entry
and add another 'struct hist_entry_ops' for 2) processing
to carry the block data for each hist_entry
jirka
next prev parent reply other threads:[~2019-06-11 8:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 14:36 [PATCH v2 0/7] perf diff: diff cycles at basic block level Jin Yao
2019-06-03 6:51 ` Jin, Yao
2019-06-03 14:36 ` [PATCH v2 1/7] perf util: Create block_info structure Jin Yao
2019-06-03 14:36 ` [PATCH v2 2/7] perf util: Add block_info in hist_entry Jin Yao
2019-06-03 14:36 ` [PATCH v2 3/7] perf diff: Check if all data files with branch stacks Jin Yao
2019-06-03 14:36 ` [PATCH v2 4/7] perf diff: Use hists to manage basic blocks per symbol Jin Yao
2019-06-05 11:44 ` Jiri Olsa
2019-06-06 1:15 ` Jin, Yao
2019-06-08 11:41 ` Jin, Yao
2019-06-11 2:22 ` Jin, Yao
2019-06-11 8:56 ` Jiri Olsa [this message]
2019-06-12 6:11 ` Jin, Yao
2019-06-12 7:44 ` Jiri Olsa
2019-06-12 12:54 ` Jin, Yao
2019-06-05 11:44 ` Jiri Olsa
2019-06-06 1:26 ` Jin, Yao
2019-06-05 11:44 ` Jiri Olsa
2019-06-06 1:57 ` Jin, Yao
2019-06-03 14:36 ` [PATCH v2 5/7] perf diff: Link same basic blocks among different data files Jin Yao
2019-06-03 14:36 ` [PATCH v2 6/7] perf diff: Print the basic block cycles diff Jin Yao
2019-06-05 11:44 ` Jiri Olsa
2019-06-06 4:06 ` Jin, Yao
2019-06-05 11:44 ` Jiri Olsa
2019-06-06 2:02 ` Jin, Yao
2019-06-03 14:36 ` [PATCH v2 7/7] perf diff: Documentation -c cycles option Jin Yao
2019-06-05 11:44 ` [PATCH v2 0/7] perf diff: diff cycles at basic block level Jiri Olsa
2019-06-06 1:05 ` Jin, Yao
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=20190611085606.GA11510@krava \
--to=jolsa@redhat.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=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.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