From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Jesper Dangaard Brouer <jbrouer@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@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@kernel.org>,
Joanne Koong <joannelkoong@gmail.com>,
Jiri Olsa <jolsa@kernel.org>,
Dave Marchevsky <davemarchevsky@fb.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Geliang Tang <geliang.tang@suse.com>,
Jakub Sitnicki <jakub@cloudflare.com>,
Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next] bpf: Add BPF-helper for accessing CLOCK_TAI
Date: Wed, 3 Aug 2022 11:28:50 +0200 [thread overview]
Message-ID: <Yuo/0hVGQcpTPxZD@boxer> (raw)
In-Reply-To: <87edxxg7qu.fsf@kurt>
On Wed, Aug 03, 2022 at 08:29:29AM +0200, Kurt Kanzenbach wrote:
> On Tue Aug 02 2022, Alexei Starovoitov wrote:
> > On Tue, Aug 2, 2022 at 12:06 AM Kurt Kanzenbach <kurt@linutronix.de> wrote:
> >>
> >> Hi Alexei,
> >>
> >> On Tue Jun 07 2022, Alexei Starovoitov wrote:
> >> > Anyway I guess new helper bpf_ktime_get_tai_ns() is ok, since
> >> > it's so trivial, but selftest is necessary.
> >>
> >> So, I did write a selftest [1] for testing bpf_ktime_get_tai_ns() and
> >> verifying that the access to the clock works. It uses AF_XDP sockets and
> >> timestamps the incoming packets. The timestamps are then validated in
> >> user space.
> >>
> >> Since AF_XDP related code is migrating from libbpf to libxdp, I'm
> >> wondering if that sample fits into the kernel's selftests or not. What
> >> kind of selftest are you looking for?
> >
> > Please use selftests/bpf framework.
> > There are plenty of networking tests in there.
> > bpf_ktime_get_tai_ns() doesn't have to rely on af_xdp.
>
> OK.
>
> > It can be skb based.
FWIW there is xskxceiver and libbpf's xsk part in selftests/bpf framework,
so your initial work should be fine in there. Personally I found both
(AF_XDP and SKB one, below) tests valuable.
Later on, if we add a support to xskxceiver for loading external BPF progs
then your sample would just become another test case in there.
>
> Something like this?
>
> +++ b/tools/testing/selftests/bpf/prog_tests/check_tai.c
> @@ -0,0 +1,57 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright (C) 2022 Linutronix GmbH */
> +
> +#include <test_progs.h>
> +#include <network_helpers.h>
> +
> +#include <time.h>
> +#include <stdint.h>
> +
> +#define TAI_THRESHOLD 1000000000ULL /* 1s */
> +#define NSEC_PER_SEC 1000000000ULL
> +
> +static __u64 ts_to_ns(const struct timespec *ts)
> +{
> + return ts->tv_sec * NSEC_PER_SEC + ts->tv_nsec;
> +}
> +
> +void test_tai(void)
> +{
> + struct __sk_buff skb = {
> + .tstamp = 0,
> + .hwtstamp = 0,
> + };
> + LIBBPF_OPTS(bpf_test_run_opts, topts,
> + .data_in = &pkt_v4,
> + .data_size_in = sizeof(pkt_v4),
> + .ctx_in = &skb,
> + .ctx_size_in = sizeof(skb),
> + .ctx_out = &skb,
> + .ctx_size_out = sizeof(skb),
> + );
> + struct timespec now_tai;
> + struct bpf_object *obj;
> + int ret, prog_fd;
> +
> + ret = bpf_prog_test_load("./test_tai.o",
> + BPF_PROG_TYPE_SCHED_CLS, &obj, &prog_fd);
> + if (!ASSERT_OK(ret, "load"))
> + return;
> + ret = bpf_prog_test_run_opts(prog_fd, &topts);
> + ASSERT_OK(ret, "test_run");
> +
> + /* TAI != 0 */
> + ASSERT_NEQ(skb.tstamp, 0, "tai_ts0_0");
> + ASSERT_NEQ(skb.hwtstamp, 0, "tai_ts0_1");
> +
> + /* TAI is moving forward only */
> + ASSERT_GT(skb.hwtstamp, skb.tstamp, "tai_forward");
> +
> + /* Check for reasoneable range */
> + ret = clock_gettime(CLOCK_TAI, &now_tai);
> + ASSERT_EQ(ret, 0, "tai_gettime");
> + ASSERT_TRUE((ts_to_ns(&now_tai) - skb.hwtstamp) < TAI_THRESHOLD,
> + "tai_range");
> +
> + bpf_object__close(obj);
> +}
> diff --git a/tools/testing/selftests/bpf/progs/test_tai.c b/tools/testing/selftests/bpf/progs/test_tai.c
> new file mode 100644
> index 000000000000..34ac4175e29d
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/test_tai.c
> @@ -0,0 +1,17 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright (C) 2022 Linutronix GmbH */
> +
> +#include <linux/bpf.h>
> +#include <bpf/bpf_helpers.h>
> +
> +char _license[] SEC("license") = "GPL";
> +
> +SEC("tc")
> +int save_tai(struct __sk_buff *skb)
> +{
> + /* Save TAI timestamps */
> + skb->tstamp = bpf_ktime_get_tai_ns();
> + skb->hwtstamp = bpf_ktime_get_tai_ns();
> +
> + return 0;
> +}
next prev parent reply other threads:[~2022-08-03 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 10:37 [PATCH bpf-next] bpf: Add BPF-helper for accessing CLOCK_TAI Kurt Kanzenbach
2022-06-06 15:57 ` Alexei Starovoitov
2022-06-07 9:14 ` Thomas Gleixner
2022-06-07 19:35 ` Jesper Dangaard Brouer
2022-06-08 2:01 ` Alexei Starovoitov
2022-06-08 6:13 ` Kurt Kanzenbach
2022-08-02 7:06 ` Kurt Kanzenbach
2022-08-02 15:03 ` Alexei Starovoitov
2022-08-03 6:29 ` Kurt Kanzenbach
2022-08-03 9:28 ` Maciej Fijalkowski [this message]
2022-08-03 17:29 ` Andrii Nakryiko
2022-08-03 17:28 ` Andrii Nakryiko
2022-08-04 6:40 ` Kurt Kanzenbach
2022-08-09 0:28 ` Andrii Nakryiko
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=Yuo/0hVGQcpTPxZD@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=geliang.tang@suse.com \
--cc=jakub@cloudflare.com \
--cc=jbrouer@redhat.com \
--cc=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kurt@linutronix.de \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).