linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Andi Kleen <andi@firstfloor.org>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"namhyung@kernel.org" <namhyung@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [BUG] perf: intel_pt won't display kernel function
Date: Wed, 3 Apr 2019 16:27:56 +0000	[thread overview]
Message-ID: <B07CAAC3-D085-443D-BB0C-05E9A8F3AFB2@fb.com> (raw)
In-Reply-To: <20190403151548.GF32553@kernel.org>



> On Apr 3, 2019, at 8:15 AM, Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
> 
> Em Wed, Apr 03, 2019 at 11:53:53AM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Wed, Apr 03, 2019 at 04:37:38PM +0200, Jiri Olsa escreveu:
>>> hi,
>>> perf script --call-trace stop working for me recently,
>>> and displays only user space functions
>>> 
>>> I bisected that to:
>>>  7b612e291a5a perf tools: Synthesize PERF_RECORD_* for loaded BPF programs
>>> 
>>> data from following comands will display user space functions only:
>>>  # perf-with-kcore record pt -e intel_pt// -- ls
>>>  # perf-with-kcore script pt --call-trace
>>> 
>>> when I disable the bpf synthesizing (patch below), kernel functions are back
>>> 
>>> I guess the new events mess up with intel_pt decoder somehow
>> 
>> I.e. I'm adding the patch below to my perf/urgent branch.
> 
> Song, that is what I have, can I have your Acked-by and please consider
> taking a look at the bug Jiri reported,
> 
> Thanks,
> 
> - Arnaldo

Current logic with --no-bpf-event is to generate PERF_RECORD_KSYMBOL, but not
PERF_RECORD_BPF_EVENT:

https://elixir.bootlin.com/linux/v5.1-rc3/source/tools/perf/util/bpf-event.c#L254

I will look into the intel_pt problem. 

In the meanwhile, let's fix it for now. 

Acked-by: Song Liu <songliubraving@fb.com>

Thanks, 
Song


> commit 011318ccc2024ba03e96c32a06f74ca5d6ab5503
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date:   Wed Apr 3 12:05:15 2019 -0300
> 
>    perf record: Do not synthesize BPF records when --no-bpf-event is used
> 
>    By default we synthesize and ask the kernel for BPF events, having a
>    --no-bpf-event option to disable that, which can be useful, for
>    instance, if there are still bugs in that code, which seems to be the
>    case as reported by Jiri Olsa in:
> 
>      "[BUG] perf: intel_pt won't display kernel function"
>      https://lore.kernel.org/lkml/20190403143738.GB32001@krava
> 
>    So add the check for record_opts.no_bpf_event when considering
>    synthesizing BPF events for pre-existing BPF programs in 'perf record'.
> 
>    The reported bug needs further analysis and is a separate matter.
> 
>    Cc: Adrian Hunter <adrian.hunter@intel.com>
>    Cc: Alexei Starovoitov <ast@kernel.org>
>    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
>    Cc: Daniel Borkmann <daniel@iogearbox.net>
>    Cc: Jiri Olsa <jolsa@kernel.org>
>    Cc: Martin KaFai Lau <kafai@fb.com>
>    Cc: Namhyung Kim <namhyung@kernel.org>
>    Cc: Peter Zijlstra <peterz@infradead.org>
>    Cc: Song Liu <songliubraving@fb.com>
>    Cc: Yonghong Song <yhs@fb.com>
>    Fixes: 7b612e291a5a ("perf tools: Synthesize PERF_RECORD_* for loaded BPF programs")
>    Link: https://lore.kernel.org/lkml/20190403145353.GE32553@kernel.org
>    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 4e2d953d4bc5..17d772f192ad 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -1114,10 +1114,11 @@ static int record__synthesize(struct record *rec, bool tail)
> 		return err;
> 	}
> 
> -	err = perf_event__synthesize_bpf_events(session, process_synthesized_event,
> -						machine, opts);
> -	if (err < 0)
> -		pr_warning("Couldn't synthesize bpf events.\n");
> +	if (!opts->no_bpf_event) {
> +		err = perf_event__synthesize_bpf_events(session, process_synthesized_event, machine, opts);
> +		if (err < 0)
> +			pr_warning("Couldn't synthesize bpf events.\n");
> +	}
> 
> 	err = __machine__synthesize_threads(machine, tool, &opts->target, rec->evlist->threads,
> 					    process_synthesized_event, opts->sample_address,


  reply	other threads:[~2019-04-03 16:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 14:37 [BUG] perf: intel_pt won't display kernel function Jiri Olsa
2019-04-03 14:53 ` Arnaldo Carvalho de Melo
2019-04-03 15:15   ` Arnaldo Carvalho de Melo
2019-04-03 16:27     ` Song Liu [this message]
2019-04-03 18:50       ` Arnaldo Carvalho de Melo
2019-04-03 18:55         ` Song Liu
2019-04-03 18:59           ` Song Liu
2019-04-03 21:48             ` Song Liu
2019-04-04  9:14               ` Jiri Olsa
2019-04-04 12:25                 ` Jiri Olsa
2019-04-04 17:08                   ` Song Liu
2019-04-04 17:38                     ` Jiri Olsa
2019-04-03 17:05 ` Song Liu
2019-04-03 18:10   ` Jiri Olsa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B07CAAC3-D085-443D-BB0C-05E9A8F3AFB2@fb.com \
    --to=songliubraving@fb.com \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).