linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, gleb@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] hung_task: add method to reset detector
Date: Tue, 8 Oct 2013 09:35:32 -0400	[thread overview]
Message-ID: <20131008133532.GQ227855@redhat.com> (raw)
In-Reply-To: <20131008010552.713337492@amt.cnet>

On Mon, Oct 07, 2013 at 10:05:16PM -0300, Marcelo Tosatti wrote:
> In certain occasions it is possible for a hung task detector
> positive to be false: continuation from a paused VM, for example.
> 
> Add a method to reset detection, similar as is done
> with other kernel watchdogs.

This makes sense to me.  Should we throw the 'reset_hung_task_detector' in
include/linux/sched.h like some of the other watchdog functions?  Or is
having a small hung_task.h file like this fine?

Cheers,
Don

> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> 
> Index: kvm/kernel/hung_task.c
> ===================================================================
> --- kvm.orig/kernel/hung_task.c
> +++ kvm/kernel/hung_task.c
> @@ -203,6 +203,14 @@ int proc_dohung_task_timeout_secs(struct
>  	return ret;
>  }
>  
> +static atomic_t reset_hung_task = ATOMIC_INIT(0);
> +
> +void reset_hung_task_detector(void)
> +{
> +	atomic_set(&reset_hung_task, 1);
> +}
> +EXPORT_SYMBOL_GPL(reset_hung_task_detector);
> +
>  /*
>   * kthread which checks for tasks stuck in D state
>   */
> @@ -216,6 +224,9 @@ static int watchdog(void *dummy)
>  		while (schedule_timeout_interruptible(timeout_jiffies(timeout)))
>  			timeout = sysctl_hung_task_timeout_secs;
>  
> +		if (atomic_xchg(&reset_hung_task, 0))
> +			continue;
> +
>  		check_hung_uninterruptible_tasks(timeout);
>  	}
>  
> Index: kvm/include/linux/hung_task.h
> ===================================================================
> --- /dev/null
> +++ kvm/include/linux/hung_task.h
> @@ -0,0 +1,15 @@
> +/*
> + *  linux/include/linux/hung_task.h
> + */
> +#ifndef LINUX_HUNG_TASK_H
> +#define LINUX_HUNG_TASK_H
> +
> +#ifdef CONFIG_DETECT_HUNG_TASK
> +void reset_hung_task_detector(void);
> +#else
> +static inline void reset_hung_task_detector(void)
> +{
> +}
> +#endif
> +
> +#endif
> 
> 

  reply	other threads:[~2013-10-08 13:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  1:05 [patch 0/3] generic kernel watchdog reset at pvclock read Marcelo Tosatti
2013-10-08  1:05 ` [patch 1/3] hung_task: add method to reset detector Marcelo Tosatti
2013-10-08 13:35   ` Don Zickus [this message]
2013-10-08  1:05 ` [patch 2/3] pvclock: detect watchdog reset at pvclock read Marcelo Tosatti
2013-10-08  9:58   ` Paolo Bonzini
2013-10-09  1:22     ` Marcelo Tosatti
2013-10-09  8:39       ` Paolo Bonzini
2013-10-08 13:37   ` Don Zickus
2013-10-08 22:08     ` Marcelo Tosatti
2013-10-09 13:55       ` Don Zickus
2013-10-09 21:26         ` Marcelo Tosatti
2013-10-16 18:22           ` Don Zickus
2013-10-08  1:05 ` [patch 3/3] 01-hung-task-watchdog-reset 02-kvmclock-touch-watchdog-on-kvmclock-read series Marcelo Tosatti
2013-10-08  1:07   ` Marcelo Tosatti
2013-10-08  9:57 ` [patch 0/3] generic kernel watchdog reset at pvclock read Paolo Bonzini
2013-10-12  0:39 ` [patch 0/2] generic kernel watchdog reset at pvclock read (v2) Marcelo Tosatti
2013-10-12  0:39   ` [patch 1/2] pvclock: detect watchdog reset at pvclock read Marcelo Tosatti
2013-10-12  0:39   ` [patch 2/2] hung_task: add method to reset detector Marcelo Tosatti
2013-10-14 11:30   ` [patch 0/2] generic kernel watchdog reset at pvclock read (v2) Paolo Bonzini
2013-10-16 18:25   ` Don Zickus
2013-10-16 21:02     ` Marcelo Tosatti
2013-11-06  7:49   ` Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131008133532.GQ227855@redhat.com \
    --to=dzickus@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).