From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42513) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdAei-00047i-0V for qemu-devel@nongnu.org; Tue, 20 Dec 2011 20:07:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RdAeg-0005KM-Kz for qemu-devel@nongnu.org; Tue, 20 Dec 2011 20:07:39 -0500 Received: from [222.73.24.84] (port=64635 helo=song.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdAeg-0005Jy-64 for qemu-devel@nongnu.org; Tue, 20 Dec 2011 20:07:38 -0500 Message-ID: <4EF13206.4050902@cn.fujitsu.com> Date: Wed, 21 Dec 2011 09:10:30 +0800 From: Wen Congyang MIME-Version: 1.0 References: <4EF04D58.3030900@cn.fujitsu.com> <4EF0522D.4040906@cn.fujitsu.com> <4EF0B711.6070909@redhat.com> In-Reply-To: <4EF0B711.6070909@redhat.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [RFC][PATCH 8/8 v3] introduce a new monitor command 'dump' to dump guest's memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Jan Kiszka , HATAYAMA Daisuke , Dave Anderson , qemu-devel At 12/21/2011 12:25 AM, Eric Blake Write: > On 12/20/2011 02:15 AM, Wen Congyang wrote: >> Signed-off-by: Wen Congyang >> --- >> Makefile.target | 8 +- >> dump.c | 452 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> dump.h | 4 + >> hmp-commands.hx | 16 ++ >> monitor.c | 3 + >> qmp-commands.hx | 24 +++ >> 6 files changed, 503 insertions(+), 4 deletions(-) >> create mode 100644 dump.c >> >> +++ b/qmp-commands.hx >> @@ -469,6 +469,30 @@ Notes: >> EQMP >> >> { >> + .name = "dump", >> + .args_type = "file:s", >> + .params = "file", >> + .help = "dump to file", >> + .user_print = monitor_user_noop, >> + .mhandler.cmd_new = do_dump, >> + }, > > From a libvirt perspective, we would like the option to be able to pass > in an already-open fd rather than just a file name. This is possible if > the 'file' argument is required to start with '/' for an absolute path, > vs. 'file:name' for an fd previously passed in via the getfd monitor > command. file:s means the parameter is a file, and the type is string. s can be file:path or fd:fd's name here. Sorry for confusing you. > > Also, does this command block? It sounds like it is long-running, which > means it probably needs to be asynchronous, as well as issue an event > upon completion, so that other monitor commands can be issued in the > meantime. > Good idea, i will try to implement it in the next version. Thanks Wen Congyang