From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Horms <horms@verge.net.au>,
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, 1 Aug 2006 11:15:38 +0300 [thread overview]
Message-ID: <20060801081538.GA4774@rhun.haifa.ibm.com> (raw)
In-Reply-To: <b808c6b7a7245fcc9593d368e2e11c87@cl.cam.ac.uk>
On Tue, Aug 01, 2006 at 09:03:10AM +0100, Keir Fraser wrote:
>
> On 1 Aug 2006, at 04:11, Akio Takebe wrote:
>
> >In the case of linux, crash_kexec() is occured by "sysrq c".
> >In the case of DomainU on xen, Help is occured by "sysrq c" now.
> >So The way of dumping DomainU's memory manualy is nothing.
>
> I don't think we're going to modify a previously untouched Linux file
> to add support for this.
If we were using a proper Linux kernel tree and not the sparse tree
this wouldn't have been a problem...
(sorry, couldn't resist)
Cheers,
Muli
next prev parent reply other threads:[~2006-08-01 8:15 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
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 [this message]
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=20060801081538.GA4774@rhun.haifa.ibm.com \
--to=muli@il.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=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.