From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XwSP0-0004xg-BM for qemu-devel@nongnu.org; Thu, 04 Dec 2014 04:08:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XwSOt-0000xs-Fj for qemu-devel@nongnu.org; Thu, 04 Dec 2014 04:08:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48771) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XwSOt-0000xN-9U for qemu-devel@nongnu.org; Thu, 04 Dec 2014 04:08:39 -0500 From: Markus Armbruster References: <1416991272-10277-1-git-send-email-bdpayne@acm.org> <1417033667-10364-1-git-send-email-bdpayne@acm.org> <1417033667-10364-2-git-send-email-bdpayne@acm.org> <20141127020403.GA7921@fam-t430.nay.redhat.com> Date: Thu, 04 Dec 2014 10:08:32 +0100 In-Reply-To: (Bryan D. Payne's message of "Wed, 3 Dec 2014 19:37:40 -0800") Message-ID: <874mtbdbov.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH] qmp: extend QMP to provide read/write access to physical memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Bryan D. Payne" Cc: Fam Zheng , qemu-devel@nongnu.org, lcapitulino@redhat.com "Bryan D. Payne" writes: >> >> Out of curiosity, what are existing solutions? >> > > Basically just attaching gdb and pulling memory out manually (or writing a > program to do the same). Can you explain again why the existing commands to read guest memory (from the top of my head: dump-guest-memory, memsave, pmemsave) are insufficient? How does your solution improve on them? What exactly can it do what these commands can't? What exactly can't it do what these commands can? I feel we need to understand the answers to these questions to sensibly evolve the API in this area. [...]