From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [for-next][PATCH 1/5] tracepoint: Give priority to probes of tracepoints
Date: Fri, 30 Oct 2015 20:49:04 +0000 (UTC) [thread overview]
Message-ID: <1968393667.16190.1446238144885.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20151030162537.6409d174@gandalf.local.home>
----- On Oct 30, 2015, at 4:25 PM, rostedt rostedt@goodmis.org wrote:
> On Thu, 29 Oct 2015 17:52:16 +0000 (UTC)
> Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
>
>> ----- On Oct 29, 2015, at 3:07 AM, rostedt rostedt@goodmis.org wrote:
>>
>> > From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
>> >
>> > In order to guarantee that a probe will be called before other probes that
>> > are attached to a tracepoint, there needs to be a mechanism to provide
>> > priority of one probe over the others.
>> >
>> > Adding a prio field to the struct tracepoint_func, which lets the probes be
>> > sorted by the priority set in the structure. If no priority is specified,
>> > then a priority of 10 is given (this is a macro, and perhaps may be changed
>> > in the future).
>> >
>> > Now probes may be added to affect other probes that are attached to a
>> > tracepoint with a guaranteed order.
>> >
>> > One use case would be to allow tracing of tracepoints be able to filter by
>> > pid. A special (higher priority probe) may be added to the sched_switch
>> > tracepoint and set the necessary flags of the other tracepoints to notify
>> > them if they should be traced or not. In case a tracepoint is enabled at the
>> > sched_switch tracepoint too, the order of the two are not random.
>> >
>> > Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>> > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>>
>> Sounds good to me,
>>
>> Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>
>
> Thanks.
>
> Unfortunately I already pushed it out to linux-next (had a deadline),
> otherwise I could have added your ack. I'm guessing you missed the RFC
> version I posted a week ago.
No worries,
I've seen it, but was busy with other stuff.
Thanks,
Mathieu
>
> -- Steve
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-10-30 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 7:07 [for-next][PATCH 0/5] tracing: Addition of set_event_pid Steven Rostedt
2015-10-29 7:07 ` [for-next][PATCH 1/5] tracepoint: Give priority to probes of tracepoints Steven Rostedt
2015-10-29 17:52 ` Mathieu Desnoyers
2015-10-30 20:25 ` Steven Rostedt
2015-10-30 20:49 ` Mathieu Desnoyers [this message]
2015-10-29 7:07 ` [for-next][PATCH 2/5] tracing: Add set_event_pid directory for future use Steven Rostedt
2015-11-19 23:24 ` Paul E. McKenney
2015-11-20 4:17 ` Steven Rostedt
2015-12-01 18:12 ` Paul E. McKenney
2015-10-29 7:07 ` [for-next][PATCH 3/5] tracing: Implement event pid filtering Steven Rostedt
2015-10-29 7:07 ` [for-next][PATCH 4/5] tracing: Check all tasks on each CPU when filtering pids Steven Rostedt
2015-10-30 6:16 ` Jiaxing Wang
2015-10-30 20:28 ` Steven Rostedt
2015-10-29 7:07 ` [for-next][PATCH 5/5] tracing: Fix sparse RCU warning Steven Rostedt
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=1968393667.16190.1446238144885.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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
Powered by JetHome