All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, wim@iguana.be
Cc: wim@iguana.be, Ian Campbell <ian.campbell@citrix.com>,
	Wouter de Geus <benv-xensource.com@junerules.com>,
	xen-devel <xen-devel@lists.xen.org>,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] watchdog/xen: don't unconditionally enable the watchdog during resume
Date: Wed, 21 Mar 2012 13:23:32 -0400	[thread overview]
Message-ID: <20120321172332.GA5923@phenom.dumpdata.com> (raw)
In-Reply-To: <4F670AC9020000780007934F@nat28.tlf.novell.com>

On Mon, Mar 19, 2012 at 09:30:33AM +0000, Jan Beulich wrote:
> This was found to be a problem particularly after guest migration.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Reported-by: Wouter de Geus <benv-xensource.com@junerules.com>
> Reported-by: Ian Campbell <Ian.Campbell@citrix.com>
> Tested-by: Wouter de Geus <benv-xensource.com@junerules.com>

Looks good to me.

Wim, would you like me to carry it for 3.4 or are you OK doing it?

Thanks!
> 
> ---
>  drivers/watchdog/xen_wdt.c |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> --- 3.3/drivers/watchdog/xen_wdt.c
> +++ 3.3-xen-watchdog-resume/drivers/watchdog/xen_wdt.c
> @@ -299,11 +299,18 @@ static void xen_wdt_shutdown(struct plat
>  
>  static int xen_wdt_suspend(struct platform_device *dev, pm_message_t state)
>  {
> -	return xen_wdt_stop();
> +	typeof(wdt.id) id = wdt.id;
> +	int rc = xen_wdt_stop();
> +
> +	wdt.id = id;
> +	return rc;
>  }
>  
>  static int xen_wdt_resume(struct platform_device *dev)
>  {
> +	if (!wdt.id)
> +		return 0;
> +	wdt.id = 0;
>  	return xen_wdt_start();
>  }
>  
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: linux-watchdog@vger.kernel.org, wim@iguana.be,
	Wouter de Geus <benv-xensource.com@junerules.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] watchdog/xen: don't unconditionally enable the watchdog during resume
Date: Wed, 21 Mar 2012 13:23:32 -0400	[thread overview]
Message-ID: <20120321172332.GA5923@phenom.dumpdata.com> (raw)
In-Reply-To: <4F670AC9020000780007934F@nat28.tlf.novell.com>

On Mon, Mar 19, 2012 at 09:30:33AM +0000, Jan Beulich wrote:
> This was found to be a problem particularly after guest migration.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Reported-by: Wouter de Geus <benv-xensource.com@junerules.com>
> Reported-by: Ian Campbell <Ian.Campbell@citrix.com>
> Tested-by: Wouter de Geus <benv-xensource.com@junerules.com>

Looks good to me.

Wim, would you like me to carry it for 3.4 or are you OK doing it?

Thanks!
> 
> ---
>  drivers/watchdog/xen_wdt.c |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> --- 3.3/drivers/watchdog/xen_wdt.c
> +++ 3.3-xen-watchdog-resume/drivers/watchdog/xen_wdt.c
> @@ -299,11 +299,18 @@ static void xen_wdt_shutdown(struct plat
>  
>  static int xen_wdt_suspend(struct platform_device *dev, pm_message_t state)
>  {
> -	return xen_wdt_stop();
> +	typeof(wdt.id) id = wdt.id;
> +	int rc = xen_wdt_stop();
> +
> +	wdt.id = id;
> +	return rc;
>  }
>  
>  static int xen_wdt_resume(struct platform_device *dev)
>  {
> +	if (!wdt.id)
> +		return 0;
> +	wdt.id = 0;
>  	return xen_wdt_start();
>  }
>  
> 
> 

  reply	other threads:[~2012-03-21 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  9:30 [PATCH] watchdog/xen: don't unconditionally enable the watchdog during resume Jan Beulich
2012-03-19  9:30 ` Jan Beulich
2012-03-21 17:23 ` Konrad Rzeszutek Wilk [this message]
2012-03-21 17:23   ` Konrad Rzeszutek Wilk
2012-03-21 19:07   ` Wim Van Sebroeck
2012-03-21 19:07     ` Wim Van Sebroeck

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=20120321172332.GA5923@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=benv-xensource.com@junerules.com \
    --cc=ian.campbell@citrix.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wim@iguana.be \
    --cc=xen-devel@lists.xen.org \
    /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 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.