[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131210154748.GA1950@gmail.com>
Date: Tue, 10 Dec 2013 16:47:48 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Alexei Starovoitov <ast@...mgrid.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Andi Kleen <andi@...stfloor.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Tom Zanussi <tom.zanussi@...ux.intel.com>,
Jovi Zhangwei <jovi.zhangwei@...il.com>,
Eric Dumazet <edumazet@...gle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH tip 0/5] tracing filters with BPF
* Alexei Starovoitov <ast@...mgrid.com> wrote:
> > I'm fine if it becomes a requirement to have a vmlinux built with
> > DEBUG_INFO to use BPF and have a tool like perf to translate the
> > filters. But it that must not replace what the current filters do
> > now. That is, it can be an add on, but not a replacement.
>
> Of course. tracing filters via bpf is an additional tool for kernel
> debugging. bpf by itself has use cases beyond tracing.
Well, Steve has a point: forcing DEBUG_INFO is a big showstopper for
most people.
Would it be possible to make BFP filters recognize exposed details
like the current filters do, without depending on the vmlinux?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists