On Thu, Dec 18, 2014 at 1:48 PM, Sedat Dilek wrote:
> Hi,
>
> I am following the "frequent lockups in 3.18rc4" thread (see [0]).
>
> So, people still work on it, and one fixlet was going towards the sched/x86.
> Is there an update of your patchset [1] (especially of patch 2/2 [2]) around?
>
> One
On Thu, Dec 18, 2014 at 1:48 PM, Sedat Dilek sedat.di...@gmail.com wrote:
Hi,
I am following the frequent lockups in 3.18rc4 thread (see [0]).
So, people still work on it, and one fixlet was going towards the sched/x86.
Is there an update of your patchset [1] (especially of patch 2/2 [2])
Hi,
I am following the "frequent lockups in 3.18rc4" thread (see [0]).
So, people still work on it, and one fixlet was going towards the sched/x86.
Is there an update of your patchset [1] (especially of patch 2/2 [2]) around?
One good thing in the discussion of [0] would be a short summarize
Hi,
I am following the frequent lockups in 3.18rc4 thread (see [0]).
So, people still work on it, and one fixlet was going towards the sched/x86.
Is there an update of your patchset [1] (especially of patch 2/2 [2]) around?
One good thing in the discussion of [0] would be a short summarize and
Here is the reworked fix against the missing preemption check that Linus
reported + the need_resched() loop pulled up to __schedule() callers also
suggested by him.
Thanks.
Frederic Weisbecker (2):
sched: Fix missing preemption check in cond_resched()
sched: Pull resched loop to __schedule()
Here is the reworked fix against the missing preemption check that Linus
reported + the need_resched() loop pulled up to __schedule() callers also
suggested by him.
Thanks.
Frederic Weisbecker (2):
sched: Fix missing preemption check in cond_resched()
sched: Pull resched loop to __schedule()
6 matches
Mail list logo