From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, Hou Tao <houtao1@huawei.com>,
bpf@vger.kernel.org, Martin KaFai Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Daniel Xu <dxu@dxuuu.xyz>
Subject: Re: [PATCHv2 bpf-next 7/9] selftests/bpf: Add test for missed counts of perf event link kprobe
Date: Sun, 10 Sep 2023 20:54:06 +0200 [thread overview]
Message-ID: <ZP4Qzo5O1mQTurJ4@krava> (raw)
In-Reply-To: <CAEf4BzZwqq73Gj9pr9A52E2fXbm_Pn+oXX7qmTzw8hEuikK3kw@mail.gmail.com>
On Fri, Sep 08, 2023 at 04:25:30PM -0700, Andrii Nakryiko wrote:
SNIP
> > +/*
> > + * Putting kprobe on bpf_fentry_test1 that calls bpf_kfunc_common_test
> > + * kfunc, which has also kprobe on. The latter won't get triggered due
> > + * to kprobe recursion check and kprobe missed counter is incremented.
> > + */
> > +static void test_missed_perf_kprobe(void)
> > +{
> > + LIBBPF_OPTS(bpf_test_run_opts, topts);
> > + struct bpf_link_info info = {};
> > + struct missed_kprobe *skel;
> > + __u32 len = sizeof(info);
> > + int err, prog_fd;
> > +
> > + skel = missed_kprobe__open_and_load();
> > + if (!ASSERT_OK_PTR(skel, "missed_kprobe__open_and_load"))
> > + goto cleanup;
> > +
> > + err = missed_kprobe__attach(skel);
> > + if (!ASSERT_OK(err, "missed_kprobe__attach"))
> > + goto cleanup;
> > +
> > + prog_fd = bpf_program__fd(skel->progs.trigger);
> > + err = bpf_prog_test_run_opts(prog_fd, &topts);
> > + ASSERT_OK(err, "test_run");
> > + ASSERT_EQ(topts.retval, 0, "test_run");
> > +
> > + err = bpf_link_get_info_by_fd(bpf_link__fd(skel->links.test2), &info, &len);
> > + if (!ASSERT_OK(err, "bpf_link_get_info_by_fd"))
> > + goto cleanup;
> > +
> > + ASSERT_EQ(info.type, BPF_LINK_TYPE_PERF_EVENT, "info.type");
> > + ASSERT_EQ(info.perf_event.type, BPF_PERF_EVENT_KPROBE, "info.perf_event.type");
> > + ASSERT_EQ(info.perf_event.kprobe.missed, 1, "info.perf_event.kprobe.missed");
> > +
> > +cleanup:
> > + missed_kprobe__destroy(skel);
> > +}
> > +
> > +void serial_test_missed(void)
>
> why serial? if you check for kprobe.missed >= 1, it should be fine
> even if some other test calls this testmod kfunc, right?
hm, I think the reason for me was the testmod getting unloaded
in serial_test_bpf_mod_race test.. but it's serial, so I guess
we should be fine
thanks,
jirka
next prev parent reply other threads:[~2023-09-10 18:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 7:13 [PATCHv2 bpf-next 0/9] bpf: Add missed stats for kprobes Jiri Olsa
2023-09-07 7:13 ` [PATCHv2 bpf-next 1/9] bpf: Count stats for kprobe_multi programs Jiri Olsa
2023-09-07 18:09 ` Song Liu
2023-09-07 7:13 ` [PATCHv2 bpf-next 2/9] bpf: Add missed value to kprobe_multi link info Jiri Olsa
2023-09-07 18:15 ` Song Liu
2023-09-07 7:13 ` [PATCHv2 bpf-next 3/9] bpf: Add missed value to kprobe perf " Jiri Olsa
2023-09-07 18:40 ` Song Liu
2023-09-08 11:43 ` Jiri Olsa
2023-09-08 16:49 ` Song Liu
2023-09-10 18:54 ` Jiri Olsa
2023-09-08 23:22 ` Andrii Nakryiko
2023-09-08 23:32 ` Song Liu
2023-09-08 23:44 ` Andrii Nakryiko
2023-09-10 18:54 ` Jiri Olsa
2023-09-07 7:13 ` [PATCHv2 bpf-next 4/9] bpf: Count missed stats in trace_call_bpf Jiri Olsa
2023-09-07 18:46 ` Song Liu
2023-09-07 7:13 ` [PATCHv2 bpf-next 5/9] bpftool: Display missed count for kprobe_multi link Jiri Olsa
2023-09-07 7:13 ` [PATCHv2 bpf-next 6/9] bpftool: Display missed count for kprobe perf link Jiri Olsa
2023-09-07 7:13 ` [PATCHv2 bpf-next 7/9] selftests/bpf: Add test for missed counts of perf event link kprobe Jiri Olsa
2023-09-07 18:52 ` Song Liu
2023-09-08 23:25 ` Andrii Nakryiko
2023-09-10 18:54 ` Jiri Olsa [this message]
2023-09-07 7:13 ` [PATCHv2 bpf-next 8/9] selftests/bpf: Add test for recursion " Jiri Olsa
2023-09-07 18:55 ` Song Liu
2023-09-14 7:56 ` Jiri Olsa
2023-09-07 7:13 ` [PATCHv2 bpf-next 9/9] selftests/bpf: Add test for recursion counts of perf event link tracepoint Jiri Olsa
2023-09-07 19:00 ` Song Liu
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=ZP4Qzo5O1mQTurJ4@krava \
--to=olsajiri@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@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