From: Horms <horms@verge.net.au>
To: Akio Takebe <takebe_akio@jp.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Kouya Shimura <kouya@jp.fujitsu.com>
Subject: Re: [Patch] Enable "sysrq c" handler for domU coredump
Date: Tue, 1 Aug 2006 15:48:06 +0900 [thread overview]
Message-ID: <20060801064805.GA14886@verge.net.au> (raw)
In-Reply-To: <4FC6B524762864takebe_akio@jp.fujitsu.com>
On Tue, Aug 01, 2006 at 01:39:23PM +0900, Akio Takebe wrote:
> 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?
Sorry, I was not clear.
Yes, my patch is to panic (or more recently cause a crash dump)
in the hypervisor. It does not give any special behaviour to
the domains.
What I meant was, that the idea of adding a panic to domU's sysrq
is similar to my idea of adding panic to the xen console. And I was
asked to change this patch to make it trigger a kdump directly,
rather than a panic.
I think that your sysrq patch and my xen-console panic patches
are related, and I wanted to bring that into the discussion.
> >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().
Right, but it does this using panic() which does have some effect
in regular Linux. I am just wondering if your solution answers
a more generic question than how to dump domU.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
next prev parent reply other threads:[~2006-08-01 6:48 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
2006-08-01 6:48 ` Horms [this message]
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=20060801064805.GA14886@verge.net.au \
--to=horms@verge.net.au \
--cc=kouya@jp.fujitsu.com \
--cc=takebe_akio@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.