Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule()

2015-09-29 Thread Peter Zijlstra
On Tue, Sep 29, 2015 at 11:30:26AM -0400, Steven Rostedt wrote: > On Tue, 29 Sep 2015 11:28:39 -0400 > Steven Rostedt wrote: > > > On Tue, 29 Sep 2015 11:28:30 +0200 > > Peter Zijlstra wrote: > > > > > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > > > path and that is

Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule()

2015-09-29 Thread Steven Rostedt
On Tue, 29 Sep 2015 11:28:39 -0400 Steven Rostedt wrote: > On Tue, 29 Sep 2015 11:28:30 +0200 > Peter Zijlstra wrote: > > > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > > path and that is to circumvent the task->state check. Since the code > > setting PREEMPT_ACTIVE i

Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule()

2015-09-29 Thread Steven Rostedt
On Tue, 29 Sep 2015 11:28:30 +0200 Peter Zijlstra wrote: > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > path and that is to circumvent the task->state check. Since the code > setting PREEMPT_ACTIVE is the immediate caller of __schedule() we can > replace this with a fun

Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule()

2015-09-29 Thread Frederic Weisbecker
On Tue, Sep 29, 2015 at 11:28:30AM +0200, Peter Zijlstra wrote: > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > path and that is to circumvent the task->state check. Since the code > setting PREEMPT_ACTIVE is the immediate caller of __schedule() we can > replace this with

Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule()

2015-09-29 Thread Thomas Gleixner
On Tue, 29 Sep 2015, Peter Zijlstra wrote: > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > path and that is to circumvent the task->state check. Since the code > setting PREEMPT_ACTIVE is the immediate caller of __schedule() we can > replace this with a function argument.