xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH v3 0/2] Improvements for domain_crash_synchronous
Date: Mon, 30 Sep 2013 18:46:54 +0100	[thread overview]
Message-ID: <1380563216-16968-1-git-send-email-andrew.cooper3@citrix.com> (raw)

This patch series provides improvements for identifying the cause of a
domain_crash_synchronous from assembly code.

There are minimal changes from v2, and again are all in the second patch.
More tweaks to the printed string, and a less ambiguous name of the label
before entering the UNLIKELY() section.

~Andrew

-- 
1.7.10.4

             reply	other threads:[~2013-09-30 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 17:46 Andrew Cooper [this message]
2013-09-30 17:46 ` [Patch v3 1/2] x86/traps: Record last extable faulting address Andrew Cooper
2013-09-30 17:46 ` [Patch v3 2/2] Xen/x86: Improve information from domain_crash_synchronous Andrew Cooper

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=1380563216-16968-1-git-send-email-andrew.cooper3@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@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).