public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Song Liu <songliubraving@fb.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	Kernel Team <Kernel-team@fb.com>,
	Peter Ziljstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [RFC 2/2] perf-stat: enable counting events for BPF programs
Date: Wed, 25 Nov 2020 17:42:36 +0100	[thread overview]
Message-ID: <20201125164236.GM2164284@krava> (raw)
In-Reply-To: <86F842B0-BF89-4418-BA2E-F93E50726A81@fb.com>

On Tue, Nov 24, 2020 at 11:31:49PM +0000, Song Liu wrote:
> 
> 
> > On Nov 23, 2020, at 3:47 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> 
> [...]
> 
> > 
> > I still need to review this deeply, but so far I'm getting this error:
> > 
> > 	# ./perf stat -b 40
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: elf: skipping unrecognized data section(9) .eh_frame
> > 	libbpf: elf: skipping relo section(15) .rel.eh_frame for section(9) .eh_frame
> > 	libbpf: XXX is not found in vmlinux BTF
> > 	libbpf: failed to load object 'bpf_prog_profiler_bpf'
> > 	libbpf: failed to load BPF skeleton 'bpf_prog_profiler_bpf': -2
> > 	libbpf: Can't get the 0th fd from program fentry_XXX: only -1 instances
> > 	libbpf: prog 'fentry_XXX': can't attach before loaded
> > 	libbpf: failed to auto-attach program 'fentry_XXX': -22
> 
> I cannot reproduce this. Is 40 a valid BPF program ID? Could you please share 
> more information about it with "bpftool prog show id 40"?

it was bpftrace kfunc program, I'll try again and get back with
more details if there's still the problem

jirka


  reply	other threads:[~2020-11-25 16:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  4:50 [RFC 0/2] Introduce perf-stat -b for BPF programs Song Liu
2020-11-19  4:50 ` [RFC 1/2] perf: support build BPF skeletons with perf Song Liu
2020-11-22 23:27   ` Jiri Olsa
2020-11-24 23:47     ` Song Liu
2020-11-25 16:38       ` Jiri Olsa
2020-11-22 23:32   ` Jiri Olsa
2020-11-24 23:51     ` Song Liu
2020-11-22 23:35   ` Jiri Olsa
2020-11-24 23:52     ` Song Liu
2020-11-25 16:40       ` Jiri Olsa
2020-11-24 19:51   ` Jiri Olsa
2020-11-24 23:59     ` Song Liu
2020-11-24 19:51   ` Jiri Olsa
2020-11-24 23:53     ` Song Liu
2020-11-19  4:50 ` [RFC 2/2] perf-stat: enable counting events for BPF programs Song Liu
2020-11-23 23:47   ` Jiri Olsa
2020-11-24 23:31     ` Song Liu
2020-11-25 16:42       ` Jiri Olsa [this message]
2020-11-24 19:51   ` Jiri Olsa
2020-11-24 23:43     ` Song Liu
2020-11-25  0:02       ` Song Liu
2020-11-25 16:43         ` Jiri Olsa
2020-11-19 14:52 ` [RFC 0/2] Introduce perf-stat -b " Arnaldo Carvalho de Melo

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=20201125164236.GM2164284@krava \
    --to=jolsa@redhat.com \
    --cc=Kernel-team@fb.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=songliubraving@fb.com \
    /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