From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>
Subject: Introducing the Xen Crashdump Analyser
Date: Wed, 20 Feb 2013 22:45:32 +0000 [thread overview]
Message-ID: <5125520C.30500@citrix.com> (raw)
Hello,
About a year ago, I started writing a tool to analyse /proc/vmcore in
the case of Xen crash (given a kdump environment) and provide a report.
The plan has always been to try and upstream it, and the main barrier
has been a lack of time on my part.
It was first released in XenServer 6.1 and has subsequently been
backported to some older versions, but I hereby formally present it to
the Xen community for comment.
Please read http://xenbits.xen.org/people/andrewcoop/ which contains
links to the source and instructions for use, as well as an example
report from a bug I am currently investigating (Scheduler race condition).
I would appreciate any feedback/queries/questions/suggestions.
Thanks,
~Andrew
reply other threads:[~2013-02-20 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5125520C.30500@citrix.com \
--to=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 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.