linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <ast@fb.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	"David S. Miller" <davem@davemloft.net>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	netdev <netdev@vger.kernel.org>, kernel-team <kernel-team@fb.com>,
	linux-api <linux-api@vger.kernel.org>,
	"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: [PATCH v5 bpf-next 06/10] tracepoint: compute num_args at build time
Date: Mon, 26 Mar 2018 13:04:43 -0400	[thread overview]
Message-ID: <20180326130443.77473b6d@gandalf.local.home> (raw)
In-Reply-To: <b07ea9b4-6b73-60aa-9391-002db42c571b@fb.com>

On Mon, 26 Mar 2018 09:47:21 -0700
Alexei Starovoitov <ast@fb.com> wrote:

> I don't mind to _rename_ for_each_kernel_tracepoint() into
> tracepoint_find_by_name(), but keeping exported function
> just to be used by out-of-tree modules would be wrong message for
> the kernel community in general.
> With my patch the for_each_kernel_tracepoint() will be used by bpf side
> and out-of-tree can trivially hack their callbacks to keep working.
> imo that's a better approach then renaming it.

Look, the tracepoint code was written by Mathieu for LTTng, and perf
and ftrace were able to benefit because of it, as well as your bpf code.
For this, we agreed to keep this function around for his use, as its the
only thing he requires. Everyone has been fine with that. Not all out
of tree code is evil. In fact, some out of tree modules help the kernel
community. You ask why I care. Because PREEMPT_RT has been one of those
out of tree modules that has helped the kernel community a lot. Have
you noticed that there are "raw_spin_lock()" and "spin_lock()"? There's
no difference between the two in the kernel. Why have them? Because
they are used by PREEMPT_RT.

Having that function for LTTng does not hurt us. And I will NACK
removing it.

-- Stevwe

  reply	other threads:[~2018-03-26 17:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180324023038.938665-1-ast@fb.com>
2018-03-26  8:28 ` [PATCH v5 bpf-next 00/10] bpf, tracing: introduce bpf raw tracepoints Daniel Borkmann
2018-03-26 15:04   ` Steven Rostedt
2018-03-26 15:32     ` Daniel Borkmann
2018-03-26 15:47       ` Steven Rostedt
2018-03-26 16:00         ` Alexei Starovoitov
2018-03-26 16:16           ` Steven Rostedt
     [not found] ` <20180324023038.938665-7-ast@fb.com>
2018-03-26 15:02   ` [PATCH v5 bpf-next 06/10] tracepoint: compute num_args at build time Steven Rostedt
2018-03-26 15:14     ` Mathieu Desnoyers
2018-03-26 15:42       ` Alexei Starovoitov
2018-03-26 15:55         ` Mathieu Desnoyers
2018-03-26 16:08           ` Alexei Starovoitov
2018-03-26 16:17             ` Mathieu Desnoyers
2018-03-26 16:25               ` Alexei Starovoitov
2018-03-26 16:35                 ` Steven Rostedt
2018-03-26 16:47                   ` Alexei Starovoitov
2018-03-26 17:04                     ` Steven Rostedt [this message]
2018-03-26 16:57                   ` Mathieu Desnoyers
2018-03-26 17:55                     ` Alexei Starovoitov
2018-03-26 18:11                       ` Steven Rostedt
2018-03-26 18:39                         ` Alexei Starovoitov
2018-03-26 18:48                           ` Steven Rostedt
2018-03-26 21:27                       ` Mathieu Desnoyers
2018-03-26 15:56   ` Steven Rostedt
2018-03-26 16:31     ` Steven Rostedt

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=20180326130443.77473b6d@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=ast@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=fche@redhat.com \
    --cc=kernel-team@fb.com \
    --cc=linux-api@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --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).