mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yang Jihong <yangjihong1@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Cc: <peterz@infradead.org>, <mingo@redhat.com>,
	<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
	<jolsa@redhat.com>, <yao.jin@linux.intel.com>,
	<gustavoars@kernel.org>, <mliska@suse.cz>,
	<linux-kernel@vger.kernel.org>, <zhangjinhao2@huawei.com>
Subject: Re: [PATCH v5] perf annotate: Fix sample events lost in stdio mode
Date: Wed, 17 Mar 2021 17:50:26 +0800	[thread overview]
Message-ID: <8d9cc941-c85e-34c2-e703-a8d52b615eff@huawei.com> (raw)
In-Reply-To: <YFCtmEBqsgKnkaV7@kernel.org>

Hello,

On 2021/3/16 21:07, Arnaldo Carvalho de Melo wrote:
> Em Tue, Mar 16, 2021 at 10:17:59AM +0800, Yang Jihong escreveu:
>> In hist__find_annotations function, since different hist_entry may point to same
>> symbol, we free notes->src to signal already processed this symbol in stdio mode;
>> when annotate, entry will skipped if notes->src is NULL to avoid repeated output.
>>
>> However, there is a problem, for example, run the following command:
>>
>>   # perf record -e branch-misses -e branch-instructions -a sleep 1
>>
>> perf.data file contains different types of sample event.
>>
>> If the same IP sample event exists in branch-misses and branch-instructions,
>> this event uses the same symbol. When annotate branch-misses events, notes->src
>> corresponding to this event is set to null, as a result, when annotate
>> branch-instructions events, this event is skipped and no annotate is output.
>>
>> Solution of this patch is to remove zfree in hists__find_annotations and
>> change sort order to "dso,symbol" to avoid duplicate output when different
>> processes correspond to the same symbol.
> 
> You forgot to add your Signed-off-by tag, i.e.:
> 
> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
> 
> Please take a look at Documentation/process/submitting-patches.rst.
> 
> Regards,
> 
> - Arnaldo
> 
Thanks for the patient instructions :)
I've submitted the v6 patch, look forward to your review:
https://lore.kernel.org/patchwork/patch/1397675

>> ---
>>   tools/perf/builtin-annotate.c | 13 ++++++-------
>>   1 file changed, 6 insertions(+), 7 deletions(-)
>>
>> diff --git a/tools/perf/builtin-annotate.c b/tools/perf/builtin-annotate.c
>> index a23ba6bb99b6..92c55f292c11 100644
>> --- a/tools/perf/builtin-annotate.c
>> +++ b/tools/perf/builtin-annotate.c
>> @@ -374,13 +374,6 @@ static void hists__find_annotations(struct hists *hists,
>>   		} else {
>>   			hist_entry__tty_annotate(he, evsel, ann);
>>   			nd = rb_next(nd);
>> -			/*
>> -			 * Since we have a hist_entry per IP for the same
>> -			 * symbol, free he->ms.sym->src to signal we already
>> -			 * processed this symbol.
>> -			 */
>> -			zfree(&notes->src->cycles_hist);
>> -			zfree(&notes->src);
>>   		}
>>   	}
>>   }
>> @@ -619,6 +612,12 @@ int cmd_annotate(int argc, const char **argv)
>>   
>>   	setup_browser(true);
>>   
>> +	/*
>> +	 * Events of different processes may correspond to the same
>> +	 * symbol, we do not care about the processes in annotate,
>> +	 * set sort order to avoid repeated output.
>> +	 */
>> +	sort_order = "dso,symbol";
>>   	if ((use_browser == 1 || annotate.use_stdio2) && annotate.has_br_stack) {
>>   		sort__mode = SORT_MODE__BRANCH;
>>   		if (setup_sorting(annotate.session->evlist) < 0)
>> -- 
>> 2.30.GIT
>>
> 

      reply	other threads:[~2021-03-17  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  2:17 Yang Jihong
2021-03-16 13:07 ` Arnaldo Carvalho de Melo
2021-03-17  9:50   ` Yang Jihong [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=8d9cc941-c85e-34c2-e703-a8d52b615eff@huawei.com \
    --to=yangjihong1@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=gustavoars@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=mliska@suse.cz \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yao.jin@linux.intel.com \
    --cc=zhangjinhao2@huawei.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

Powered by JetHome