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 v4 4/7] perf diff: Use hists to manage basic blocks per symbol
Date: Wed, 26 Jun 2019 08:57:30 +0800 [thread overview]
Message-ID: <b8e461e9-e835-539b-119a-698e774194af@linux.intel.com> (raw)
In-Reply-To: <20190625091134.GD9574@krava>
On 6/25/2019 5:11 PM, Jiri Olsa wrote:
> On Thu, Jun 20, 2019 at 10:36:39PM +0800, Jin Yao wrote:
>
> SNIP
>
>> +
>> +static void *block_entry_zalloc(size_t size)
>> +{
>> + return zalloc(size + sizeof(struct hist_entry));
>> +}
>> +
>> +static void block_entry_free(void *he)
>> +{
>> + struct block_info *bi = ((struct hist_entry *)he)->block_info;
>> +
>> + block_info__put(bi);
>> + free(he);
>> +}
>
> so if we carry block_info in 'struct hist_entry' we don't need
> to use our own allocation in the 2nd level hist entries.. just
> for the first level to carry the new 'struct block_hists'
>
> the block_info should be released in hist_entry__delete then,
> same as for other *info pointers
>
> the rest of the patchset looks ok to me
>
> thanks,
> jirka
>
Yes, releasing the block_info in hist_entry__delete is a better way.
Thanks Jiri, I will update the patch.
Thanks
Jin Yao
>> +
>> +struct hist_entry_ops block_entry_ops = {
>> + .new = block_entry_zalloc,
>> + .free = block_entry_free,
>> +};
>> +
>> +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,
>> + &block_entry_ops,
>> + &dummy_al, bi);
>> + if (!he_block) {
>> + block_info__put(bi);
>> + return -1;
>> + }
>> + }
>> + }
>> +
>> + return 0;
>
> SNIP
>
next prev parent reply other threads:[~2019-06-26 0:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 14:36 [PATCH v4 0/7] perf diff: diff cycles at basic block level Jin Yao
2019-06-20 14:36 ` [PATCH v4 1/7] perf util: Create block_info structure Jin Yao
2019-06-20 14:36 ` [PATCH v4 2/7] perf util: Add block_info in hist_entry Jin Yao
2019-06-20 14:36 ` [PATCH v4 3/7] perf diff: Check if all data files with branch stacks Jin Yao
2019-06-20 14:36 ` [PATCH v4 4/7] perf diff: Use hists to manage basic blocks per symbol Jin Yao
2019-06-24 7:57 ` Jiri Olsa
2019-06-24 14:49 ` Jin, Yao
2019-06-25 8:50 ` Jiri Olsa
2019-06-25 9:11 ` Jiri Olsa
2019-06-26 0:57 ` Jin, Yao [this message]
2019-06-20 14:36 ` [PATCH v4 5/7] perf diff: Link same basic blocks among different data Jin Yao
2019-06-20 14:36 ` [PATCH v4 6/7] perf diff: Print the basic block cycles diff Jin Yao
2019-06-20 14:36 ` [PATCH v4 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=b8e461e9-e835-539b-119a-698e774194af@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