From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: xen/conring: Improvements
Date: Tue, 6 Aug 2013 15:07:20 +0100 [thread overview]
Message-ID: <52010318.2090508@citrix.com> (raw)
In-Reply-To: <1375280572-15203-1-git-send-email-andrew.cooper3@citrix.com>
On 31/07/13 15:22, Andrew Cooper wrote:
> These two changes have come from an investgation of a cascade crash
> deliberatly triggered using an NMI from an IPMI controller. As the NMI/MCE/DF
> stack trace is particularly important to be captured in the crash environment,
> I recomend these patches for backport to all Xen trees.
>
> ~Andrew
Ping?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-08-06 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 14:22 xen/conring: Improvements Andrew Cooper
2013-07-31 14:22 ` [PATCH 1/2] xen/conring: Clean up writing to the console ring Andrew Cooper
2013-07-31 18:12 ` Matt Wilson
2013-08-06 14:43 ` Keir Fraser
2013-07-31 14:22 ` [PATCH 2/2] xen/conring: Write to console ring even if console lock is busted Andrew Cooper
2013-07-31 18:15 ` Matt Wilson
2013-08-06 14:44 ` Keir Fraser
2013-08-06 14:07 ` Andrew Cooper [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=52010318.2090508@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--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).