[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cjyN_sxMe9yajgnuDRy5234NZQ5sd0e4ynBmCnQSv=WFQ@mail.gmail.com>
Date: Thu, 9 Dec 2021 15:39:20 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Michael Petlan <mpetlan@...hat.com>,
Ian Rogers <irogers@...gle.com>,
linux-perf-users <linux-perf-users@...r.kernel.org>,
"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: [RFC] perf record: Disable debuginfod by default
Hi Jiri,
On Thu, Dec 9, 2021 at 12:04 PM Jiri Olsa <jolsa@...hat.com> wrote:
>
> hi,
> after migrating to fedora 35 I found perf record hanging on exit
> and it's because fedora 35 sets DEBUGINFOD_URLS that triggers
> debuginfod query which might take long time to process.
>
> I discussed this briefly with Frank and I'm sending the change
> to disable debuginfod by default in perf record.
>
> Frank had other idea we could discuss here to fork or just spawn
> "/usr/bin/debuginfod-find ...." into background after perf record.
>
> Perhaps there are other ways as well, hence this is RFC ;-)
I thought the debuginfod was for perf report, not record.
Maybe I'm missing something but how about moving it to
report? We can talk to debuginfod after checking the local
build-id cache and binary on the system.
Still, we can have perf buildid-cache to move it from the
debuginfod to local cache.
Thanks,
Namhyung
Powered by blists - more mailing lists