From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Horms <horms@verge.net.au>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
xen-devel <xen-devel@lists.xensource.com>,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
Kouya Shimura <kouya@jp.fujitsu.com>,
Tristan Gingold <Tristan.Gingold@bull.net>
Subject: Re: [Patch][RFC] Support "xm dump" (is Re: Re: [Patch] Enable "sysrq c" handler for domU coredump)
Date: Thu, 03 Aug 2006 20:10:29 +0900 [thread overview]
Message-ID: <6CC6B6ED6DBDFDtakebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <20060803015000.GG12456@verge.net.au>
Hi, Horms
Thank you for your comments.
This is very helpful.
>> diff -r 10b05c2e7947 -r a16cc49dbd01 tools/libxc/xenctrl.h
>> --- a/tools/libxc/xenctrl.h Tue Aug 01 18:08:01 2006 +0100
>> +++ b/tools/libxc/xenctrl.h Thu Aug 03 09:20:16 2006 +0900
>> @@ -202,6 +202,17 @@ int xc_domain_unpause(int xc_handle,
>> uint32_t domid);
>>
>> /**
>> + * This function dump a domain. A domain_dump only crash domain.
>> + * after crash domain, xc_domain_dumpcore dump domain memory.
>
>Perhaps:
>
> /**
> * This function dumps a domain to a core file. It does this by
> * crashing the domain, after which xc_domain_dumpcore() will dump the
> * domain's memory.
>
Yes, you are right.
Your comments is very clear.
I use your comments. :)
>> @@ -945,6 +950,13 @@ static PyMethodDef pyxc_methods[] = {
>> "Dump core of a domain.\n"
>> " dom [int]: Identifier of domain to dump core of.\n"
>> " corefile [string]: Name of corefile to be created.\n\n"
>> + "Returns: [int] 0 on success; -1 on error.\n" },
>> +
>> + { "domain_dump",
>> + (PyCFunction)pyxc_domain_dump,
>> + METH_VARARGS, "\n"
>> + "Dump of a domain.\n"
>
>The description sof domain_dumpcore vs domain_dump above
>are somewhat ambigious. Could you make it clearer what
>the difference between the two is?
>
>Perhaps:
> "Crash a domain so that it will dump core\n"
>
Yes, this is also good.
Best Regards,
Akio Takebe
next prev parent reply other threads:[~2006-08-03 11:10 UTC|newest]
Thread overview: 27+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 14:45 [Patch][RFC] Support "xm dump" (is Re: Re: [Patch]Enable "sysrq c" handler for domU coredump) Graham, Simon
2006-08-03 15:24 ` [Patch][RFC] Support "xm dump" (is Re: " Akio Takebe
2006-08-08 12:31 ` John Levon
2006-08-08 15:00 ` Akio Takebe
2006-08-03 21:52 Graham, Simon
2006-08-04 9:58 ` [Patch][RFC] Support "xm dump" (is " Akio Takebe
2006-08-04 10:29 ` Harry Butterworth
2006-08-04 13:58 [Patch][RFC] Support "xm dump" (is " Graham, Simon
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=6CC6B6ED6DBDFDtakebe_akio@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=Tristan.Gingold@bull.net \
--cc=horms@verge.net.au \
--cc=kouya@jp.fujitsu.com \
--cc=muli@il.ibm.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.