Re: watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/27/2017 04:58 AM, Niklas Cassel wrote: On 02/27/2017 05:04 AM, Guenter Roeck wrote: On Fri, Feb 17, 2017 at 07:25:02PM +0100, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit

Re: watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/27/2017 04:58 AM, Niklas Cassel wrote: On 02/27/2017 05:04 AM, Guenter Roeck wrote: On Fri, Feb 17, 2017 at 07:25:02PM +0100, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let

[PATCH v2] watchdog: softdog: fire watchdog even if softirqs do not get to run

From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending softirqs, and ksoftirqd is

[PATCH v2] watchdog: softdog: fire watchdog even if softirqs do not get to run

From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,

Re: watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/27/2017 05:04 AM, Guenter Roeck wrote: > On Fri, Feb 17, 2017 at 07:25:02PM +0100, Niklas Cassel wrote: >> From: Niklas Cassel >> >> Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. >> >> Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its

Re: watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/27/2017 05:04 AM, Guenter Roeck wrote: > On Fri, Feb 17, 2017 at 07:25:02PM +0100, Niklas Cassel wrote: >> From: Niklas Cassel >> >> Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. >> >> Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), >> pending

Re: watchdog: softdog: fire watchdog even if softirqs do not get to run

On Fri, Feb 17, 2017 at 07:25:02PM +0100, Niklas Cassel wrote: > From: Niklas Cassel > > Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. > > Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), > pending softirqs are no longer always

Re: watchdog: softdog: fire watchdog even if softirqs do not get to run

On Fri, Feb 17, 2017 at 07:25:02PM +0100, Niklas Cassel wrote: > From: Niklas Cassel > > Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. > > Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), > pending softirqs are no longer always handled immediately,

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead,

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/20/2017 02:03 AM, Niklas Cassel wrote: On 02/19/2017 05:46 PM, Guenter Roeck wrote: Cc: Wolfram for input. On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/20/2017 02:03 AM, Niklas Cassel wrote: On 02/19/2017 05:46 PM, Guenter Roeck wrote: Cc: Wolfram for input. On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/20/2017 12:36 AM, Peter Zijlstra wrote: On Sun, Feb 19, 2017 at 08:46:28AM -0800, Guenter Roeck wrote: Cc: Wolfram for input. On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/20/2017 12:36 AM, Peter Zijlstra wrote: On Sun, Feb 19, 2017 at 08:46:28AM -0800, Guenter Roeck wrote: Cc: Wolfram for input. On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/19/2017 05:46 PM, Guenter Roeck wrote: > Cc: Wolfram for input. > > On 02/17/2017 10:25 AM, Niklas Cassel wrote: >> From: Niklas Cassel >> >> Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. >> >> Since commit 4cd13c21b207 ("softirq: Let

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On 02/19/2017 05:46 PM, Guenter Roeck wrote: > Cc: Wolfram for input. > > On 02/17/2017 10:25 AM, Niklas Cassel wrote: >> From: Niklas Cassel >> >> Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. >> >> Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), >>

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On Sun, Feb 19, 2017 at 08:46:28AM -0800, Guenter Roeck wrote: > Cc: Wolfram for input. > > On 02/17/2017 10:25 AM, Niklas Cassel wrote: > >From: Niklas Cassel > > > >Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. > > > >Since commit 4cd13c21b207

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

On Sun, Feb 19, 2017 at 08:46:28AM -0800, Guenter Roeck wrote: > Cc: Wolfram for input. > > On 02/17/2017 10:25 AM, Niklas Cassel wrote: > >From: Niklas Cassel > > > >Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. > > > >Since commit 4cd13c21b207 ("softirq: Let ksoftirqd

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

Cc: Wolfram for input. On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled

Re: [PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

Cc: Wolfram for input. On 02/17/2017 10:25 AM, Niklas Cassel wrote: From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead,

[PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending softirqs, and ksoftirqd is

[PATCH] watchdog: softdog: fire watchdog even if softirqs do not get to run

From: Niklas Cassel Checking for timer expiration is done from the softirq TIMER_SOFTIRQ. Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"), pending softirqs are no longer always handled immediately, instead, if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,