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
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
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
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
4 matches
Mail list logo