From: Keir Fraser <keir.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: Re: Xen watchdog improvements
Date: Mon, 12 Aug 2013 17:50:25 +0100 [thread overview]
Message-ID: <CE2ED0E1.5A819%keir.xen@gmail.com> (raw)
In-Reply-To: <1376314680-12548-1-git-send-email-andrew.cooper3@citrix.com>
On 12/08/2013 14:37, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> This series offers some improvements to Xen watchdogs.
>
> Patch 1 moves the concept of a watchdog from x86 specific code to common.
> Patch 2 tweaks the x86 implementation, given the common implementation.
> Patch 3 is a bugfix for certain cases where the watchdog code interacts badly
> with
> console_force_unlock().
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Tim Deegan <tim@xen.org>
With v2 of patch 2:
Acked-by: Keir Fraser <keir@xen.org>
prev parent reply other threads:[~2013-08-12 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 13:37 Xen watchdog improvements Andrew Cooper
2013-08-12 13:37 ` [PATCH 1/3] xen/watchdog: Move watchdog from being x86 specific to common code Andrew Cooper
2013-08-12 13:37 ` [PATCH 2/3] x86/watchdog: Tweak implementation given new " Andrew Cooper
2013-08-12 13:49 ` Jan Beulich
2013-08-12 13:54 ` Andrew Cooper
2013-08-12 14:03 ` [Patch v2 " Andrew Cooper
2013-08-12 13:38 ` [PATCH 3/3] watchdog/crash: Always disable watchdog in console_force_unlock() Andrew Cooper
2013-08-12 13:47 ` Xen watchdog improvements Josh Zhao
2013-08-12 15:20 ` Andrew Cooper
2013-08-12 13:51 ` Jan Beulich
2013-08-12 16:50 ` Keir Fraser [this message]
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=CE2ED0E1.5A819%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--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 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).