From: Yonghong Song <yhs@fb.com>
To: Joe Stringer <joe@cilium.io>, <bpf@vger.kernel.org>
Cc: <daniel@iogearbox.net>, <ast@kernel.org>,
Lorenz Bauer <lmb@cloudflare.com>,
Song Liu <songliubraving@fb.com>,
Stanislav Fomichev <sdf@google.com>
Subject: Re: [PATCH bpf-next] bpf: Document PROG_TEST_RUN limitations
Date: Sun, 11 Apr 2021 09:22:16 -0700 [thread overview]
Message-ID: <ef619573-377f-a6c1-3a2f-477d2284fa3a@fb.com> (raw)
In-Reply-To: <20210410174549.816482-1-joe@cilium.io>
On 4/10/21 10:45 AM, Joe Stringer wrote:
> Per net/bpf/test_run.c, particular prog types have additional
> restrictions around the parameters that can be provided, so document
> these in the header.
>
> I didn't bother documenting the limitation on duration for raw
> tracepoints since that's an output parameter anyway.
>
> Tested with ./tools/testing/selftests/bpf/test_doc_build.sh.
>
> Suggested-by: Yonghong Song <yhs@fb.com>
> Signed-off-by: Joe Stringer <joe@cilium.io>
> ---
> CC: Lorenz Bauer <lmb@cloudflare.com>
> CC: Song Liu <songliubraving@fb.com>
> CC: Stanislav Fomichev <sdf@google.com>
Thanks for the fix of the doc.
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2021-04-11 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 17:45 [PATCH bpf-next] bpf: Document PROG_TEST_RUN limitations Joe Stringer
2021-04-11 16:22 ` Yonghong Song [this message]
2021-04-12 9:02 ` Lorenz Bauer
2021-04-12 15:40 ` patchwork-bot+netdevbpf
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=ef619573-377f-a6c1-3a2f-477d2284fa3a@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=joe@cilium.io \
--cc=lmb@cloudflare.com \
--cc=sdf@google.com \
--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