From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v2][RFC] tracing/context-tracking: Add preempt_schedule_context() for tracing
Date: Thu, 6 Jun 2013 12:07:52 +0200 [thread overview]
Message-ID: <20130606100752.GG8923@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1370486988.9844.24.camel@gandalf.local.home>
On Wed, Jun 05, 2013 at 10:49:48PM -0400, Steven Rostedt wrote:
> Peter,
>
> Are you fine with this answer, or do you still believe I should put it
> into sched/core.c?
Its ok I suppose. I just had to wrap my head around this
context_tracking muck; first time I ever looked at it.
> I switched it to EXPORT_SYMBOL_GPL, so that only GPL modules may use
> preempt_enable_notrace().
>
> Are you OK with this?
Yep, applied.
next prev parent reply other threads:[~2013-06-06 10:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 19:59 [PATCH][RFC] tracing/context-tracking: Add preempt_schedule_context() for tracing Steven Rostedt
2013-05-31 13:43 ` Frederic Weisbecker
2013-05-31 15:18 ` Steven Rostedt
2013-05-31 15:56 ` Frederic Weisbecker
2013-05-31 16:01 ` Peter Zijlstra
2013-05-31 16:11 ` Steven Rostedt
2013-06-01 1:30 ` [PATCH v2][RFC] " Steven Rostedt
2013-06-04 12:09 ` Frederic Weisbecker
2013-06-04 12:16 ` Steven Rostedt
2013-06-04 12:29 ` Frederic Weisbecker
2013-06-04 12:27 ` Frederic Weisbecker
2013-06-04 14:16 ` Steven Rostedt
2013-06-05 11:45 ` Peter Zijlstra
2013-06-05 13:41 ` Steven Rostedt
2013-06-06 2:49 ` Steven Rostedt
2013-06-06 10:07 ` Peter Zijlstra [this message]
2013-06-06 13:50 ` 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=20130606100752.GG8923@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.