[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b03f9794-ff84-c869-0370-e8f13c577ed5@arm.com>
Date: Thu, 5 Aug 2021 13:59:49 +0100
From: James Clark <james.clark@....com>
To: Leo Yan <leo.yan@...aro.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: mathieu.poirier@...aro.org, coresight@...ts.linaro.org,
linux-perf-users@...r.kernel.org, suzuki.poulose@....com,
mike.leach@...aro.org, Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
John Garry <john.garry@...wei.com>,
Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 6/6] perf cs-etm: Add warnings for missing DSOs
On 03/08/2021 15:01, Leo Yan wrote:
>> one can also use debuginfod-client, which, as time passes, probably will
>> be the main way of finding DSOs now that we have build-ids in
>> PERF_RECORD_MMAP2 and debuginfod servers such as:
>>
>> export DEBUGINFOD_URLS=https://debuginfod.fedoraproject.org/
> If so, maybe should use more general description for missing DSO.
>
>> https://fedoraproject.org/wiki/Debuginfod
>>
>>> With this improvement, the patch looks good to me:
>>>
>>> Reviewed-by: Leo Yan <leo.yan@...aro.org>
>> Does this apply to the other 5 patches in this series?
> I finished to reivew patches 01, 04, 05, 06/06, so my review tag can
> apply on these patches. Current patch 06/06 needs James to improve for
> the comments.
Thanks for the reviews, I've submitted v2.
I also had a play around with debuginfod, it looks promising.
Especially if it's integrated with perf report, which I assume is the plan?
Thanks
James
Powered by blists - more mailing lists