All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] [PATCH]: Reset clocksource watchdog after sysrq-t
@ 2011-11-02 13:46 Prarit Bhargava
  2011-12-01  4:08 ` Xiaochen Wang
  0 siblings, 1 reply; 2+ messages in thread
From: Prarit Bhargava @ 2011-11-02 13:46 UTC (permalink / raw)
  To: linux-kernel; +Cc: Prarit Bhargava, tglx, johnstul

When doing a sysrq-t other processes are starved out because the task_list
lock is held.  On a large enough system this means that the clocksource
watchdog does not fire for a long time and when system operation resumes the
watchdog erroneously marks the current clocksource as unstable.

Reset the clocksource watchdog after show_state_filter() has dumped the
task states.

Cc: tglx@linutronix.de
Cc: johnstul@us.ibm.com
---
 kernel/sched.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/kernel/sched.c b/kernel/sched.c
index d87c6e5..b09c053 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -71,6 +71,7 @@
 #include <linux/ctype.h>
 #include <linux/ftrace.h>
 #include <linux/slab.h>
+#include <linux/clocksource.h>
 
 #include <asm/tlb.h>
 #include <asm/irq_regs.h>
@@ -6034,6 +6035,7 @@ void show_state_filter(unsigned long state_filter)
 	} while_each_thread(g, p);
 
 	touch_all_softlockup_watchdogs();
+	clocksource_touch_watchdog();
 
 #ifdef CONFIG_SCHED_DEBUG
 	sysrq_sched_debug_show();
-- 
1.7.1


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] [PATCH]: Reset clocksource watchdog after sysrq-t
  2011-11-02 13:46 [PATCH] [PATCH]: Reset clocksource watchdog after sysrq-t Prarit Bhargava
@ 2011-12-01  4:08 ` Xiaochen Wang
  0 siblings, 0 replies; 2+ messages in thread
From: Xiaochen Wang @ 2011-12-01  4:08 UTC (permalink / raw)
  To: Prarit Bhargava; +Cc: linux-kernel, tglx, johnstul

Hi Prarit,
    I'm reading the clocksource watchdog code, in which case I see your patch.
But i cannot understand the patch very well.

On Wed, Nov 2, 2011 at 9:46 PM, Prarit Bhargava <prarit@redhat.com> wrote:
> When doing a sysrq-t other processes are starved out because the task_list
> lock is held.  On a large enough system this means that the clocksource
> watchdog does not fire for a long time and when system operation resumes the
> watchdog erroneously marks the current clocksource as unstable.
Do you mean that a sysrq-t will enlarge the deviation between watchdog and the
 watched clocksource(in watchdog_list) ?
>
> Reset the clocksource watchdog after show_state_filter() has dumped the
> task states.
>
> Cc: tglx@linutronix.de
> Cc: johnstul@us.ibm.com
> ---
>  kernel/sched.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/sched.c b/kernel/sched.c
> index d87c6e5..b09c053 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -71,6 +71,7 @@
>  #include <linux/ctype.h>
>  #include <linux/ftrace.h>
>  #include <linux/slab.h>
> +#include <linux/clocksource.h>
>
>  #include <asm/tlb.h>
>  #include <asm/irq_regs.h>
> @@ -6034,6 +6035,7 @@ void show_state_filter(unsigned long state_filter)
>        } while_each_thread(g, p);
>
>        touch_all_softlockup_watchdogs();
> +       clocksource_touch_watchdog();
>
>  #ifdef CONFIG_SCHED_DEBUG
>        sysrq_sched_debug_show();
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Thanks,
Xiaochen

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-12-01  4:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-02 13:46 [PATCH] [PATCH]: Reset clocksource watchdog after sysrq-t Prarit Bhargava
2011-12-01  4:08 ` Xiaochen Wang

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.