From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Li Zefan <lizf@cn.fujitsu.com>, Tom Zanussi <tzanussi@gmail.com>
Subject: [PATCH 1/6] tracing: allow filter predicates to handle ksym symbols
Date: Sat, 12 Sep 2009 23:43:03 -0400 [thread overview]
Message-ID: <20090913034635.933408354@goodmis.org> (raw)
In-Reply-To: 20090913034302.134417216@goodmis.org
[-- Attachment #1: 0001-tracing-allow-filter-predicates-to-handle-ksym-symbo.patch --]
[-- Type: text/plain, Size: 1045 bytes --]
From: Steven Rostedt <srostedt@redhat.com>
This patch increases the max string used by predicates to
handle KSYM_SYMBOL_LEN.
Also moves an include to look nicer.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
include/linux/ftrace_event.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/ftrace_event.h b/include/linux/ftrace_event.h
index 0608b0f..bd099ba 100644
--- a/include/linux/ftrace_event.h
+++ b/include/linux/ftrace_event.h
@@ -1,8 +1,8 @@
#ifndef _LINUX_FTRACE_EVENT_H
#define _LINUX_FTRACE_EVENT_H
-#include <linux/trace_seq.h>
#include <linux/ring_buffer.h>
+#include <linux/trace_seq.h>
#include <linux/percpu.h>
struct trace_array;
@@ -135,7 +135,7 @@ struct ftrace_event_call {
};
#define MAX_FILTER_PRED 32
-#define MAX_FILTER_STR_VAL 128
+#define MAX_FILTER_STR_VAL 256 /* Should handle KSYM_SYMBOL_LEN */
extern void destroy_preds(struct ftrace_event_call *call);
extern int filter_match_preds(struct ftrace_event_call *call, void *rec);
--
1.6.3.3
--
next prev parent reply other threads:[~2009-09-13 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 3:43 [PATCH 0/6] [GIT PULL] tracing: automate output for ftrace formats Steven Rostedt
2009-09-13 3:43 ` Steven Rostedt [this message]
2009-09-13 3:43 ` [PATCH 2/6] tracing: use macros to create internal ftrace entry ring buffer structures Steven Rostedt
2009-09-13 3:43 ` [PATCH 3/6] tracing: show details of structures within the ftrace structures Steven Rostedt
2009-09-13 3:43 ` [PATCH 4/6] tracing: use the new trace_entries.h to create format files Steven Rostedt
2009-09-13 3:43 ` [PATCH 5/6] tracing: remove trace_event_types.h Steven Rostedt
2009-09-13 3:43 ` [PATCH 6/6] tracing: add filter event logic to special, mmiotrace and boot tracers Steven Rostedt
2009-09-13 14:59 ` [PATCH 0/6] [GIT PULL] tracing: automate output for ftrace formats Ingo Molnar
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=20090913034635.933408354@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tzanussi@gmail.com \
/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