[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ea42a459-1b73-b236-d9e3-50e4bec81de9@intel.com>
Date: Mon, 7 Oct 2019 15:14:54 +0300
From: Adrian Hunter <adrian.hunter@...el.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] perf record: Put a copy of kcore into the perf.data
directory
On 7/10/19 2:20 PM, Jiri Olsa wrote:
> On Fri, Oct 04, 2019 at 11:31:21AM +0300, Adrian Hunter wrote:
>
> SNIP
>
>> bool strict_freq;
>> bool sample_id;
>> bool no_bpf_event;
>> + bool kcore;
>> unsigned int freq;
>> unsigned int mmap_pages;
>> unsigned int auxtrace_mmap_pages;
>> diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
>> index 061bb4d6a3f5..bfa80fe8d369 100644
>> --- a/tools/perf/util/session.c
>> +++ b/tools/perf/util/session.c
>> @@ -230,6 +230,10 @@ struct perf_session *perf_session__new(struct perf_data *data,
>> if (ret)
>> goto out_delete;
>> }
>> +
>> + if (!symbol_conf.kallsyms_name &&
>> + !symbol_conf.vmlinux_name)
>> + symbol_conf.kallsyms_name = perf_data__kallsyms_name(data);
>
> hum, should this also depend on rec->opts.kcore ?
This is the bit that makes 'perf script' work. It has the same affect as
though the --kallsyms option was used. i.e. it makes 'perf script' behave
the same as:
perf script --kallsyms perf.data/kcore_dir/kallsyms
Which works because perf looks for kcore in the same directory as kallsyms.
Powered by blists - more mailing lists