From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, Yonghong Song <yhs@fb.com>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 bpf-next 2/6] bpf: add bpf_trace_vprintk helper
Date: Wed, 25 Aug 2021 17:51:52 -0700 [thread overview]
Message-ID: <CAADnVQ+SOCwcBXhdOBdHweAuP=qg4DMSvZYvJAtPefhJqn-vJg@mail.gmail.com> (raw)
In-Reply-To: <20210825195823.381016-3-davemarchevsky@fb.com>
On Wed, Aug 25, 2021 at 12:58 PM Dave Marchevsky <davemarchevsky@fb.com> wrote:
> */
> #define __BPF_FUNC_MAPPER(FN) \
> FN(unspec), \
> @@ -5048,6 +5056,7 @@ union bpf_attr {
> FN(timer_cancel), \
> FN(get_func_ip), \
> FN(get_attach_cookie), \
> + FN(trace_vprintk), \
It needs a rebase.
next prev parent reply other threads:[~2021-08-26 0:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 19:58 [PATCH v2 bpf-next 0/6] bpf: implement variadic printk helper Dave Marchevsky
2021-08-25 19:58 ` [PATCH v2 bpf-next 1/6] bpf: merge printk and seq_printf VARARG max macros Dave Marchevsky
2021-08-25 19:58 ` [PATCH v2 bpf-next 2/6] bpf: add bpf_trace_vprintk helper Dave Marchevsky
2021-08-26 0:51 ` Alexei Starovoitov [this message]
2021-08-25 19:58 ` [PATCH v2 bpf-next 3/6] libbpf: Modify bpf_printk to choose helper based on arg count Dave Marchevsky
2021-08-26 1:01 ` Alexei Starovoitov
2021-08-28 2:05 ` Dave Marchevsky
2021-08-30 23:55 ` Andrii Nakryiko
2021-09-01 23:29 ` Dave Marchevsky
2021-09-02 0:52 ` Andrii Nakryiko
2021-08-25 19:58 ` [PATCH v2 bpf-next 4/6] bpftool: only probe trace_vprintk feature in 'full' mode Dave Marchevsky
2021-08-25 19:58 ` [PATCH v2 bpf-next 5/6] selftests/bpf: Migrate prog_tests/trace_printk CHECKs to ASSERTs Dave Marchevsky
2021-08-25 19:58 ` [PATCH v2 bpf-next 6/6] selftests/bpf: add trace_vprintk test prog Dave Marchevsky
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='CAADnVQ+SOCwcBXhdOBdHweAuP=qg4DMSvZYvJAtPefhJqn-vJg@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=netdev@vger.kernel.org \
--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).