From: Keir Fraser <keir.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v2 0/2] Improvements for domain_crash_synchronous
Date: Mon, 09 Sep 2013 06:44:29 -0700 [thread overview]
Message-ID: <CE531ECD.5D1B3%keir.xen@gmail.com> (raw)
In-Reply-To: <1378730793-2420-1-git-send-email-andrew.cooper3@citrix.com>
On 09/09/2013 05:46, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> This patch series provides improvements for identifying the cause of a
> domain_crash_synchronous from assembly code.
>
> All changes for v2 are in the 2nd patch, which has been rebased on top of
> staging, now the prerequisite series have been committed.
>
> ~Andrew
Acked-by: Keir Fraser <keir@xen.org>
prev parent reply other threads:[~2013-09-09 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 12:46 [PATCH v2 0/2] Improvements for domain_crash_synchronous Andrew Cooper
2013-09-09 12:46 ` [PATCH v2 1/2] x86/traps: Record last extable faulting address Andrew Cooper
2013-09-09 12:46 ` [PATCH v2 2/2] Xen/x86: Improve information from domain_crash_synchronous Andrew Cooper
2013-09-09 13:45 ` Jan Beulich
2013-09-09 13:49 ` Andrew Cooper
2013-09-09 14:06 ` Jan Beulich
2013-09-09 13:44 ` 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=CE531ECD.5D1B3%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--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).