From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <ast@fb.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Peter Zijlstra <peterz@infradead.org>,
Network Development <netdev@vger.kernel.org>,
kernel-team <kernel-team@fb.com>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH v2 bpf-next 4/8] tracepoint: compute num_args at build time
Date: Thu, 22 Mar 2018 12:14:13 -0400 [thread overview]
Message-ID: <20180322121413.176a59f0@gandalf.local.home> (raw)
In-Reply-To: <f630fbce-dbe1-d0c3-072d-47215d5afaf3@fb.com>
On Thu, 22 Mar 2018 08:51:16 -0700
Alexei Starovoitov <ast@fb.com> wrote:
> So I definitely support the idea of build time warn for large
> number of args.
I'm more for a build time error for large number of args.
-- Steve
next prev parent reply other threads:[~2018-03-22 16:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 18:54 [PATCH v2 bpf-next 0/8] bpf, tracing: introduce bpf raw tracepoints Alexei Starovoitov
2018-03-21 18:54 ` [PATCH v2 bpf-next 1/8] treewide: remove struct-pass-by-value from tracepoints arguments Alexei Starovoitov
2018-03-21 18:54 ` [PATCH v2 bpf-next 2/8] net/mediatek: disambiguate mt76 vs mt7601u trace events Alexei Starovoitov
2018-03-21 18:54 ` [PATCH v2 bpf-next 3/8] net/mac802154: disambiguate mac80215 vs mac802154 " Alexei Starovoitov
2018-03-21 18:54 ` [PATCH v2 bpf-next 4/8] tracepoint: compute num_args at build time Alexei Starovoitov
2018-03-21 19:44 ` Linus Torvalds
2018-03-21 22:05 ` Alexei Starovoitov
2018-03-22 13:36 ` Steven Rostedt
2018-03-22 15:51 ` Alexei Starovoitov
2018-03-22 16:14 ` Steven Rostedt [this message]
2018-03-21 18:54 ` [PATCH v2 bpf-next 5/8] bpf: introduce BPF_RAW_TRACEPOINT Alexei Starovoitov
2018-03-22 9:43 ` Daniel Borkmann
2018-03-22 15:41 ` Alexei Starovoitov
2018-03-23 23:13 ` Daniel Borkmann
2018-03-24 0:58 ` Alexei Starovoitov
2018-03-24 1:43 ` Alexei Starovoitov
2018-03-24 2:01 ` Linus Torvalds
2018-03-26 7:53 ` Daniel Borkmann
2018-03-24 1:39 ` Steven Rostedt
2018-03-21 18:54 ` [PATCH v2 bpf-next 6/8] libbpf: add bpf_raw_tracepoint_open helper Alexei Starovoitov
2018-03-21 18:54 ` [PATCH v2 bpf-next 7/8] samples/bpf: raw tracepoint test Alexei Starovoitov
2018-03-21 18:54 ` [PATCH v2 bpf-next 8/8] selftests/bpf: test for bpf_get_stackid() from raw tracepoints Alexei Starovoitov
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=20180322121413.176a59f0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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).