Re: [PATCH v3] sched: Fix broken setscheduler()

2014-03-12 Thread Thomas Gleixner
On Tue, 11 Mar 2014, Steven Rostedt wrote: > > I decided to run my tests on linux-next, and my wakeup_rt tracer was > broken. After running a bisect, I found that the problem commit was: > >linux-next commit c365c292d059 >"sched: Consider pi boosting in setscheduler()" > > And the

Re: [PATCH v3] sched: Fix broken setscheduler()

2014-03-12 Thread Thomas Gleixner
On Tue, 11 Mar 2014, Steven Rostedt wrote: I decided to run my tests on linux-next, and my wakeup_rt tracer was broken. After running a bisect, I found that the problem commit was: linux-next commit c365c292d059 sched: Consider pi boosting in setscheduler() And the reason the

[PATCH v3] sched: Fix broken setscheduler()

2014-03-11 Thread Steven Rostedt
I decided to run my tests on linux-next, and my wakeup_rt tracer was broken. After running a bisect, I found that the problem commit was: linux-next commit c365c292d059 "sched: Consider pi boosting in setscheduler()" And the reason the wake_rt tracer test was failing, was because it had

[PATCH v3] sched: Fix broken setscheduler()

2014-03-11 Thread Steven Rostedt
I decided to run my tests on linux-next, and my wakeup_rt tracer was broken. After running a bisect, I found that the problem commit was: linux-next commit c365c292d059 sched: Consider pi boosting in setscheduler() And the reason the wake_rt tracer test was failing, was because it had no