From: Yang Jihong <yangjihong1@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Yao Jin <yao.jin@linux.intel.com>,
<gustavoars@kernel.org>, <mliska@suse.cz>,
linux-kernel <linux-kernel@vger.kernel.org>,
<zhangjinhao2@huawei.com>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v7] perf annotate: Fix sample events lost in stdio mode
Date: Mon, 12 Apr 2021 15:22:29 +0800 [thread overview]
Message-ID: <12d269ad-80f9-3893-f3c4-d12fcdbfecda@huawei.com> (raw)
In-Reply-To: <555b7a2d-13c8-e840-e62b-cf0ad7d084a9@huawei.com>
Hello, Arnaldo,
On 2021/3/31 10:18, Yang Jihong wrote:
> Hello, Namhyung and Arnaldo,
>
> On 2021/3/30 15:26, Namhyung Kim wrote:
>> Hi Yang and Arnaldo,
>>
>> On Sat, Mar 27, 2021 at 11:16 AM Yang Jihong <yangjihong1@huawei.com>
>> wrote:
>>> On 2021/3/26 20:06, Arnaldo Carvalho de Melo wrote:
>>>> So it seems to be working, what am I missing? Is this strictly non
>>>> group related?
>>>>
>>> Yes, it is non group related.
>>> This problem occurs only when different events need to be recorded at
>>> the same time, i.e.:
>>> perf record -e branch-misses -e branch-instructions -a sleep 1
>>>
>>> The output results of perf script and perf annotate do not match.
>>> Some events are not output in perf annotate.
>>
>> Yeah I think it's related to sort keys. The code works with a single
>> hist_entry for each event and symbol. But the default sort key
>> creates multiple entries for different threads and it causes the
>> confusion.
>>
> Yes, After revome zfree from hists__find_annotations, the output of perf
> annotate is repeated, which is related to sort keys.
>
> The original problem is that notes->src may correspond to multiple
> sample events. Therefore, we cannot simply zfree notes->src to avoid
> repeated output.
>
> Arnaldo, is there any problem with this patch? :)
>
> Thanks,
> Yang
>> Thanks,
>> Namhyung
>> .
>>
PING :)
Is there any problem with this patch that needs to be modified?
Thanks,
Yang
next prev parent reply other threads:[~2021-04-12 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 12:35 Yang Jihong
2021-03-26 2:24 ` Yang Jihong
2021-03-26 3:25 ` Namhyung Kim
2021-03-26 12:06 ` Arnaldo Carvalho de Melo
2021-03-27 2:15 ` Yang Jihong
2021-03-30 7:26 ` Namhyung Kim
2021-03-31 2:18 ` Yang Jihong
2021-04-12 7:22 ` Yang Jihong [this message]
2021-04-14 12:23 ` Arnaldo Carvalho de Melo
2021-04-14 13:15 ` Namhyung Kim
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=12d269ad-80f9-3893-f3c4-d12fcdbfecda@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
all inboxes | Powered by JetHome®