From: Li Zefan <lizf@cn.fujitsu.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tracing/filters: Support specifying filter hook to a TRACE_EVENT field
Date: Fri, 07 Aug 2009 09:08:44 +0800 [thread overview]
Message-ID: <4A7B7E9C.6060008@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908061022490.9870@gandalf.stny.rr.com>
>> [PATCH 1/3] tracing/filters: Add filter_type to struct ftrace_event_field
>> [PATCH 2/3] tracing/filters: Add __field_ext() to TRACE_EVENT
>> [PATCH 3/3] tracing/filters: Support filtering for char * strings
>
> I like the first two patches, but would like to see a V2 with the updates
> I've mentioned. The last patch I do not fully understand its purpose.
>
The last one is wanted by Frederic in his bkl trace events patchset:
http://lkml.org/lkml/2009/8/1/26
In that patch a ptr_str filter hook is always attached to "char *"
field, which is unsafe.
> I'll wait for V2 to pull it in.
>
prev parent reply other threads:[~2009-08-07 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 6:05 [PATCH 0/3] tracing/filters: Support specifying filter hook to a TRACE_EVENT field Li Zefan
2009-08-06 6:06 ` [PATCH 1/3] tracing/filters: Add filter_type to struct ftrace_event_field Li Zefan
2009-08-06 6:06 ` [PATCH 2/3] tracing/filters: Add __field_ext() to TRACE_EVENT Li Zefan
2009-08-06 14:17 ` Steven Rostedt
2009-08-06 6:06 ` [PATCH 3/3] tracing/filters: Support filtering for char * strings Li Zefan
2009-08-06 14:21 ` Steven Rostedt
2009-08-07 1:20 ` Li Zefan
2009-08-07 2:54 ` Steven Rostedt
2009-08-07 3:12 ` Li Zefan
2009-08-07 3:22 ` Steven Rostedt
2009-08-07 3:24 ` Li Zefan
2009-08-07 3:31 ` Steven Rostedt
2009-08-06 14:23 ` [PATCH 0/3] tracing/filters: Support specifying filter hook to a TRACE_EVENT field Steven Rostedt
2009-08-07 1:08 ` Li Zefan [this message]
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=4A7B7E9C.6060008@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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