From: Peter Zijlstra <peterz@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Julien Desfossez <jdesfossez@efficios.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] tracing: add sched_set_prio tracepoint
Date: Mon, 6 Jun 2016 23:03:53 +0200 [thread overview]
Message-ID: <20160606210353.GF30154@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1276244634.29549.1465242720729.JavaMail.zimbra@efficios.com>
On Mon, Jun 06, 2016 at 07:52:00PM +0000, Mathieu Desnoyers wrote:
> ----- On May 30, 2016, at 9:18 AM, Mathieu Desnoyers mathieu.desnoyers@efficios.com wrote:
> Adding Ingo and Peter in CC, considering that it touches to tracing and
> the scheduler.
> >> +/*
> >> + * Tracepoint for showing priority inheritance modifying a tasks
> >> + * priority.
> >> + */
> >> +DEFINE_EVENT(sched_prio_template, sched_pi_setprio,
> >> + TP_PROTO(struct task_struct *tsk, int newprio),
> >> + TP_ARGS(tsk, newprio));
> >> +
> >> +/*
> >> + * Tracepoint for priority changes of a task.
> >> + */
> >> +DEFINE_EVENT(sched_prio_template, sched_set_prio,
> >> + TP_PROTO(struct task_struct *tsk, int newprio),
> >> + TP_ARGS(tsk, newprio));
> >> +
Nak on anything that cannot fundamentally deal with SCHED_DEADLINE.
next prev parent reply other threads:[~2016-06-06 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 15:16 [RFC PATCH 1/2] sched: encapsulate priority changes in a sched_set_prio static function Julien Desfossez
2016-05-27 15:16 ` [RFC PATCH 2/2] tracing: add sched_set_prio tracepoint Julien Desfossez
2016-05-30 13:18 ` Mathieu Desnoyers
2016-06-06 19:52 ` Mathieu Desnoyers
2016-06-06 21:03 ` Peter Zijlstra [this message]
2016-06-08 0:18 ` Daniel Bristot de Oliveira
2016-05-30 13:18 ` [RFC PATCH 1/2] sched: encapsulate priority changes in a sched_set_prio static function Mathieu Desnoyers
2016-06-06 21:47 ` Mathieu Desnoyers
2016-06-07 7:11 ` Peter Zijlstra
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=20160606210353.GF30154@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jdesfossez@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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