netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <ast@plumgrid.com>
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>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC net-next] tracing: accelerate tracing filters with BPF
Date: Tue, 13 May 2014 23:17:08 -0400	[thread overview]
Message-ID: <20140513231708.7eb39a38@gandalf.local.home> (raw)
In-Reply-To: <1400036111-7803-1-git-send-email-ast@plumgrid.com>

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

On Tue, 13 May 2014 19:55:11 -0700
Alexei Starovoitov <ast@plumgrid.com> wrote:

> Tracing filters are parsing user supplied character string and constructing
> a predicate tree. filter_match_preds() was used to walk nodes of the tree to
> simulate matching of boolean expression.
> 

I applied this on top of net-next, from:

 git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
 (master branch)

and got this compile error:

kernel/trace/trace_events_filter.c: In function ‘emit_cond’:
kernel/trace/trace_events_filter.c:1361:36: error: ‘__bpf_call_base’ undeclared (first use in this function)
kernel/trace/trace_events_filter.c:1361:36: note: each undeclared identifier is reported only once for each function it appears in
kernel/trace/trace_events_filter.c: In function ‘filter_gen_bpf’:
kernel/trace/trace_events_filter.c:1622:2: error: implicit declaration of function ‘bpf_int_jit_compile’ [-Werror=implicit-function-declaration]

Config attached.

-- Steve

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 24766 bytes --]

  parent reply	other threads:[~2014-05-14  3:17 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
2014-05-14  5:09     ` Ingo Molnar
2014-05-14  3:17 ` Steven Rostedt [this message]
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=20140513231708.7eb39a38@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=edumazet@google.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.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).