linux-kernel.vger.kernel.org archive mirror
 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 v3 2/2] Support interactive annotation of code without symbols
Date: Mon, 24 Feb 2020 21:46:55 +0100	[thread overview]
Message-ID: <20200224204655.GB100468@krava> (raw)
In-Reply-To: <ed9fea55-1568-ab55-cf4a-52fef7c429bf@linux.intel.com>

On Mon, Feb 24, 2020 at 11:39:43PM +0800, Jin, Yao wrote:

SNIP

> > > +	sym = symbol__new(addr, ANNOTATION_DUMMY_LEN, 0, 0, name);
> > > +	if (sym) {
> > > +		src = symbol__hists(sym, 1);
> > > +		if (!src) {
> > > +			symbol__delete(sym);
> > > +			return NULL;
> > > +		}
> > 
> > hi,
> > I like the patchset:
> > 
> > Acked-by: Jiri Olsa <jolsa@redhat.com>
> > 
> > could you please also check if we can do this earlier,
> > so the dummy symbol is actualy collecting all the hits?
> > 
> > like within the symbol__inc_addr_samples function,
> > but I mght be missing something..
> > 
> > thanks,
> > jirka
> > 
> 
> Thanks so much for like and ack this patchset!
> 
> For your suggestion, I had thought about the similar idea before. Maybe we
> can, but we need to process some cases.
> 
> Say the first address is 0x1000 and the dummy symbol size is 256. We create
> a new dummy symbol for this address (start address is 0x1000 and end address
> is 0x1100).
> 
> If the second address is 0x1010, we can't create a new dummy symbol for this
> address directly. On the contrary, we need to search the dummy symbol list
> by the address first. If the dummy symbol is found then reuse this symbol.
> 
> This idea is a bit more complicated than current patchset in implementation
> but it can collect the hits for the dummy symbols, that's the advantage. The
> advantage of current patchset is it's very simple. :)

ah right, we dont know the symbol's size.. perhaps we could hold
histogram of unresolved addresses and use it later on when displaying
the annotation for the particular unresolved address.. but then
how to bucket the counts for accounting.. yep, it seems tricky ;-)

> 
> Accept current patchset or rewrite for the new idea, both OK for me. :)

I think you it can be build on top of this

thanks,
jirka


  reply	other threads:[~2020-02-24 20:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  2:22 [PATCH v3 0/2] perf report: Support annotation of code without symbols Jin Yao
2020-02-24  2:22 ` [PATCH v3 1/2] perf util: Print al_addr when symbol is not found Jin Yao
2020-02-24  2:22 ` [PATCH v3 2/2] Support interactive annotation of code without symbols Jin Yao
2020-02-24 12:35   ` Jiri Olsa
2020-02-24 15:39     ` Jin, Yao
2020-02-24 20:46       ` Jiri Olsa [this message]
2020-02-24 13:25   ` Ravi Bangoria
2020-02-24 13:51     ` Jiri Olsa
2020-02-24 14:04       ` Ravi Bangoria
2020-02-24 15:53         ` Jin, Yao
2020-02-24 15:44     ` Jin, Yao
2020-02-24 13:56   ` Ravi Bangoria
2020-02-24 15:46     ` Jin, Yao
2020-02-27 13:50 ` [PATCH v3 0/2] perf report: Support " Arnaldo Carvalho de Melo
2020-02-27 14:47   ` 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=20200224204655.GB100468@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;
as well as URLs for NNTP newsgroup(s).