[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHbLzkqMZMB7sGLbJk82CpE9cssEU+WZYaXhVTVC-B40bY52jw@mail.gmail.com>
Date: Mon, 27 Mar 2023 17:53:04 -0700
From: Yang Shi <shy828301@...il.com>
To: Leo Yan <leo.yan@...aro.org>
Cc: James Clark <james.clark@....com>,
linux-perf-users@...r.kernel.org,
LAK <linux-arm-kernel@...ts.infradead.org>,
coresight@...ts.linaro.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
mathieu.poirier@...aro.org, adrian.hunter@...el.com,
Jiri Olsa <jolsa@...nel.org>, acme@...hat.com,
mike.leach@...aro.org, Will Deacon <will@...nel.org>,
suzuki.poulose@....com, yang@...amperecomputing.com
Subject: Re: [BUG] perf: No samples found when using kcore + coresight
Hi Leo,
Just follow up on this one. Any update?
Thanks,
Yang
On Mon, Mar 13, 2023 at 5:36 PM Leo Yan <leo.yan@...aro.org> wrote:
>
> On Mon, Mar 13, 2023 at 11:15:44AM -0700, Yang Shi wrote:
>
> [...]
>
> > > Just a quick summary, here we have two issues:
> > >
> > > - With command:
> > > perf record -e cs_etm/@..._etf63/k --kcore --per-thread \
> > > -- taskset --cpu-list 1 uname",
> > >
> > > perf doesn't enable "text poke" attribution.
> >
> > No, it enables "text poke" and perf fails to decode coresight trace
> > data too. It doesn't matter whether "--kcore" is after or before "-e
> > cs/etm/@..._etf63/k".
>
> Understand now. Thanks for correction, if so we can ignore this one.
>
> Leo
Powered by blists - more mailing lists