All of lore.kernel.org
 help / color / mirror / Atom feed
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 v5 4/7] perf diff: Use hists to manage basic blocks per symbol
Date: Thu, 27 Jun 2019 09:42:27 +0200	[thread overview]
Message-ID: <20190627074227.GC24279@krava> (raw)
In-Reply-To: <ceae45ed-f1e7-ad4e-78ab-a56f0ae0d11e@linux.intel.com>

On Thu, Jun 27, 2019 at 03:34:38PM +0800, Jin, Yao wrote:
> 
> 
> On 6/27/2019 3:27 PM, Jiri Olsa wrote:
> > On Thu, Jun 27, 2019 at 10:09:26PM +0800, Jin Yao wrote:
> > 
> > SNIP
> > 
> > > +
> > > +static int process_block_per_sym(struct hist_entry *he)
> > > +{
> > > +	struct annotation *notes;
> > > +	struct cyc_hist *ch;
> > > +	struct block_hist *bh;
> > > +
> > > +	if (!he->ms.map || !he->ms.sym)
> > > +		return 0;
> > > +
> > > +	notes = symbol__annotation(he->ms.sym);
> > > +	if (!notes || !notes->src || !notes->src->cycles_hist)
> > > +		return 0;
> > > +
> > > +	bh = container_of(he, struct block_hist, he);
> > > +	init_block_hist(bh);
> > > +
> > > +	ch = notes->src->cycles_hist;
> > > +	for (unsigned int i = 0; i < symbol__size(he->ms.sym); i++) {
> > > +		if (ch[i].num_aggr) {
> > > +			struct block_info *bi;
> > > +			struct hist_entry *he_block;
> > > +
> > > +			bi = block_info__new();
> > > +			if (!bi)
> > > +				return -1;
> > > +
> > > +			init_block_info(bi, he->ms.sym, &ch[i], i);
> > > +			he_block = hists__add_entry_block(&bh->block_hists,
> > > +							  NULL, &dummy_al, bi);
> > 
> > nit, it's the only caller of hists__add_entry_block, so we don't need
> > the 'ops' argument in there
> > 
> > other than this, this all looks good to me
> > 
> > Reviewed-by: Jiri Olsa <jolsa@kernel.org>
> > 
> > thanks,
> > jirka
> > 
> 
> Hi Jiri,
> 
> Thanks so much!
> 
> Do you need me to send v6 which only removes the 'ops' argument from
> hists__add_entry_block? Or this v5 should be OK either?

please send v6, thanks

jirka

  reply	other threads:[~2019-06-27  7:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 14:09 [PATCH v5 0/7] perf diff: diff cycles at basic block level Jin Yao
2019-06-27 14:09 ` [PATCH v5 1/7] perf util: Create block_info structure Jin Yao
2019-06-27 14:09 ` [PATCH v5 2/7] perf util: Add block_info in hist_entry Jin Yao
2019-06-27 14:09 ` [PATCH v5 3/7] perf diff: Check if all data files with branch stacks Jin Yao
2019-06-27 14:09 ` [PATCH v5 4/7] perf diff: Use hists to manage basic blocks per symbol Jin Yao
2019-06-27  7:27   ` Jiri Olsa
2019-06-27  7:34     ` Jin, Yao
2019-06-27  7:42       ` Jiri Olsa [this message]
2019-06-27 14:09 ` [PATCH v5 5/7] perf diff: Link same basic blocks among different data Jin Yao
2019-06-27 14:09 ` [PATCH v5 6/7] perf diff: Print the basic block cycles diff Jin Yao
2019-06-27 14:09 ` [PATCH v5 7/7] perf diff: Documentation -c cycles option 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=20190627074227.GC24279@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 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.