Messages in this thread | | | From | Namhyung Kim <> | Date | Tue, 15 Sep 2020 11:58:16 +0900 | Subject | Re: [PATCH 09/26] perf tools: Try load vmlinux from buildid database |
| |
On Tue, Sep 15, 2020 at 5:29 AM Jiri Olsa <jolsa@redhat.com> wrote: > > On Mon, Sep 14, 2020 at 03:25:39PM +0900, Namhyung Kim wrote: > > On Mon, Sep 14, 2020 at 6:04 AM Jiri Olsa <jolsa@kernel.org> wrote: > > > > > > Currently we don't check on kernel's vmlinux the same way as > > > we do for normal binaries, but we either look for kallsyms > > > file in build id database or check on known vmlinux locations > > > (plus some other optional paths). > > > > > > This patch adds the check for standard build id binary location, > > > so we are ready once we start to store it there from debuginfod > > > in following changes. > > > > But dso__load_vmlinux_path() already has the logic. > > Also you should check symbol_conf.ignore_vmlinux_buildid. > > I wanted to have it not dependent on !symbol_conf.ignore_vmlinux > which is needed to call dso__load_vmlinux_path
Note that it's a different config variable to suppress using build-id when loading kernel DSO from perf record.
Thanks Namhyung
> > also the idea was to try the build id vmlinux before the configured > vmlinux locations, because they found the vmlinux in my setup ;-) > > I'll double check the logic again > > thanks, > jirka >
| |