From: Kip Macy <kmacy@fsmware.com>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, Chotu Ram <chotwo@hotmail.com>
Subject: Re: xm pause <domain>
Date: Sun, 23 Jan 2005 15:09:18 -0800 (PST) [thread overview]
Message-ID: <20050123150715.H63308@demos.bsdclusters.com> (raw)
In-Reply-To: <200501231441.22853.maw48@cl.cam.ac.uk>
>
> The Linux Kernel Crash Dump project (http://lkcd.sf.net) includes
> Linux-specific analysis tools that (given an LKCD-formatted dump file) can
> inspect what processes were running when a dump was taken, etc. It would be
> nice if we could dump a domain in LKCD format and thus allow these tools to
> be leveraged.
I'm about to implement the crashdump support and am thinking a bit about
the format the dump should take - is the format documented anywhere
other than the tools themselves?
-Kip
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-23 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 15:14 xm pause <domain> Chotu Ram
2005-01-23 14:41 ` Mark Williamson
2005-01-23 23:09 ` Kip Macy [this message]
2005-01-23 23:14 ` Mark Williamson
2005-01-23 23:34 ` Kip Macy
2005-01-24 0:46 ` Mark Williamson
2005-01-26 2:56 ` Kip Macy
2005-01-26 16:23 ` Mark A. Williamson
2005-01-26 16:47 ` Rolf Neugebauer
2005-01-26 17:02 ` Kip Macy
2005-01-26 19:57 ` Mark Williamson
2005-01-24 22:51 ` Daniel Stekloff
2005-01-25 13:46 ` Mark Williamson
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=20050123150715.H63308@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=chotwo@hotmail.com \
--cc=maw48@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.