On Thu, 16 Jan 2014 19:42:51 +0100
Peter Zijlstra wrote:
> Suppose a reschedule interrupt happens in the middle; we set
> NEED_RESCHED but won't act because preempt is disabled.
>
> When we hit preempt_enable() we'll call into preempt_schedule() but fail
> because preemptible() finds
On Thu, Jan 16, 2014 at 6:18 PM, Steven Rostedt wrote:
>
> Back in the original real-time patch there was a nice debug feature
> that tracked where preemption was disabled and not matched by a preempt
> enable. This information made debugging scheduling while atomic much
> easier, especially when
On Thu, Jan 16, 2014 at 01:39:06PM -0500, Steven Rostedt wrote:
> On Thu, 16 Jan 2014 18:45:36 +0100
> Peter Zijlstra wrote:
>
> > On Thu, Jan 16, 2014 at 12:18:24PM -0500, Steven Rostedt wrote:
> >
> > Didn't see anything horrible in there, so fine with me.
> >
> > Another thing I recently
On Thu, 16 Jan 2014 18:45:36 +0100
Peter Zijlstra wrote:
> On Thu, Jan 16, 2014 at 12:18:24PM -0500, Steven Rostedt wrote:
>
> Didn't see anything horrible in there, so fine with me.
>
> Another thing I recently ran into was:
>
> local_irq_disable();
> preempt_disable();
>
On Thu, Jan 16, 2014 at 12:18:24PM -0500, Steven Rostedt wrote:
Didn't see anything horrible in there, so fine with me.
Another thing I recently ran into was:
local_irq_disable();
preempt_disable();
local_irq_enable();
local_irq_disable();
preempt_enable();
local_irq_enable();
I'm
On Thu, 16 Jan 2014 12:18:24 -0500
Steven Rostedt wrote:
>
> Back in the original real-time patch there was a nice debug feature
> that tracked where preemption was disabled and not matched by a preempt
> enable. This information made debugging scheduling while atomic much
> easier, especially
Back in the original real-time patch there was a nice debug feature
that tracked where preemption was disabled and not matched by a preempt
enable. This information made debugging scheduling while atomic much
easier, especially when a function was buried in a function chain
that happened just
Back in the original real-time patch there was a nice debug feature
that tracked where preemption was disabled and not matched by a preempt
enable. This information made debugging scheduling while atomic much
easier, especially when a function was buried in a function chain
that happened just
On Thu, 16 Jan 2014 12:18:24 -0500
Steven Rostedt rost...@goodmis.org wrote:
Back in the original real-time patch there was a nice debug feature
that tracked where preemption was disabled and not matched by a preempt
enable. This information made debugging scheduling while atomic much
On Thu, Jan 16, 2014 at 12:18:24PM -0500, Steven Rostedt wrote:
Didn't see anything horrible in there, so fine with me.
Another thing I recently ran into was:
local_irq_disable();
preempt_disable();
local_irq_enable();
local_irq_disable();
preempt_enable();
local_irq_enable();
I'm
On Thu, 16 Jan 2014 18:45:36 +0100
Peter Zijlstra pet...@infradead.org wrote:
On Thu, Jan 16, 2014 at 12:18:24PM -0500, Steven Rostedt wrote:
Didn't see anything horrible in there, so fine with me.
Another thing I recently ran into was:
local_irq_disable();
preempt_disable();
On Thu, Jan 16, 2014 at 01:39:06PM -0500, Steven Rostedt wrote:
On Thu, 16 Jan 2014 18:45:36 +0100
Peter Zijlstra pet...@infradead.org wrote:
On Thu, Jan 16, 2014 at 12:18:24PM -0500, Steven Rostedt wrote:
Didn't see anything horrible in there, so fine with me.
Another thing I
On Thu, Jan 16, 2014 at 6:18 PM, Steven Rostedt rost...@goodmis.org wrote:
Back in the original real-time patch there was a nice debug feature
that tracked where preemption was disabled and not matched by a preempt
enable. This information made debugging scheduling while atomic much
easier,
On Thu, 16 Jan 2014 19:42:51 +0100
Peter Zijlstra pet...@infradead.org wrote:
Suppose a reschedule interrupt happens in the middle; we set
NEED_RESCHED but won't act because preempt is disabled.
When we hit preempt_enable() we'll call into preempt_schedule() but fail
because preemptible()
14 matches
Mail list logo
