From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Horms <horms@verge.net.au>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
Kouya Shimura <kouya@jp.fujitsu.com>
Subject: Re: [Patch] Enable "sysrq c" handler for domU coredump
Date: Tue, 01 Aug 2006 13:39:23 +0900 [thread overview]
Message-ID: <4FC6B524762864takebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <20060801034824.GD13414@verge.net.au>
Hi, Horms
>
>That seems fine to me. Though there was some resistance to a
>patch I sent which adds a panic option to xen-console, which
>is the hypervisor equivalent of sysrq.
>
This patch focus only manually dumping domU's core.
How can I use the panic option of xen-console?
I thought your patch to panic xen.
Can I dump domU's core with the option?
>Also, is this option really Xen specific. It seems it
>might be just as useful in regular Linux.
This is a patch to dump domU's core,
so Linux is not useful becaus Linux can dump by calling crash_kexec().
Best Regards,
Akio Takebe
next prev parent reply other threads:[~2006-08-01 4:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 3:11 [Patch] Enable "sysrq c" handler for domU coredump Akio Takebe
2006-08-01 3:48 ` Horms
2006-08-01 4:39 ` Akio Takebe [this message]
2006-08-01 6:48 ` Horms
2006-08-01 9:06 ` Akio Takebe
2006-08-01 9:26 ` Horms
2006-08-01 10:33 ` Akio Takebe
2006-08-03 0:18 ` [Patch][RFC] Support "xm dump" (is Re: Re: [Patch] Enable "sysrq c" handler for domU coredump) Akio Takebe
2006-08-03 0:26 ` John Levon
2006-08-03 6:09 ` Tristan Gingold
2006-08-03 11:10 ` Akio Takebe
2006-08-03 11:58 ` Tristan Gingold
2006-08-03 12:57 ` Akio Takebe
2006-08-07 18:04 ` John Levon
2006-08-03 1:50 ` Horms
2006-08-03 11:10 ` Akio Takebe
2006-08-01 8:03 ` [Patch] Enable "sysrq c" handler for domU coredump Keir Fraser
2006-08-01 8:15 ` Muli Ben-Yehuda
2006-08-01 8:12 ` Keir Fraser
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=4FC6B524762864takebe_akio@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=horms@verge.net.au \
--cc=kouya@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
/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.