From: Alexei Starovoitov <ast@plumgrid.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Daniel Borkmann <dborkman@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH RFC net-next] tracing: accelerate tracing filters with BPF
Date: Tue, 13 May 2014 20:26:10 -0700 [thread overview]
Message-ID: <CAMEtUuyHO-MGzL6nrLShG1UHTzb=HXTAPV5trv1SHL6TV0bMYw@mail.gmail.com> (raw)
In-Reply-To: <20140513230713.1cc7db94@gandalf.local.home>
On Tue, May 13, 2014 at 8:07 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 13 May 2014 19:55:11 -0700
> Alexei Starovoitov <ast@plumgrid.com> wrote:
>
>> --- a/kernel/trace/Kconfig
>> +++ b/kernel/trace/Kconfig
>> @@ -79,6 +79,7 @@ config FTRACE_NMI_ENTER
>> default y
>>
>> config EVENT_TRACING
>> + depends on NET
>> select CONTEXT_SWITCH_TRACER
>> bool
>>
>
> This part makes me a little nervous. I know a lot of embedded devices
> depend on tracing, but do they all have network?
I think we may want to split BPF into its own config, since it doesn't
really depend on anything in net.
> They may, but I would like to hear from others in the embedded space.
>
> -- Steve
next prev parent reply other threads:[~2014-05-14 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 2:55 [PATCH RFC net-next] tracing: accelerate tracing filters with BPF Alexei Starovoitov
2014-05-14 3:07 ` Steven Rostedt
2014-05-14 3:26 ` Alexei Starovoitov [this message]
2014-05-14 5:09 ` Ingo Molnar
2014-05-14 3:17 ` Steven Rostedt
2014-05-14 3:29 ` Alexei Starovoitov
2014-05-14 5:09 ` Ingo Molnar
2014-05-15 5:19 ` 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='CAMEtUuyHO-MGzL6nrLShG1UHTzb=HXTAPV5trv1SHL6TV0bMYw@mail.gmail.com' \
--to=ast@plumgrid.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=grant.likely@secretlab.ca \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).