From: "Bryan D. Payne" <bdpayne@acm.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qmp: extend QMP to provide read/write access to physical memory
Date: Thu, 4 Dec 2014 08:49:34 -0800 [thread overview]
Message-ID: <CAFpPvXC2AzXrqw3_t5+T721gp=5kF+3DAT-2Eda9kPWyjtdP=Q@mail.gmail.com> (raw)
In-Reply-To: <874mtbdbov.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
>
> 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.
Certainly. The main issue with this series of commands is that they dump
the memory to a file on disk. What I'm trying to facilitate here is an
application that monitors the guest memory in real time while the guest is
running (likely with brief pauses during memory analysis periods). Writing
all of this data to disk, and then reading it back again for the analysis
application is several orders of magnitude too slow for these types of
applications.
This new method that I'm proposing here keeps everything in memory, which
makes it much faster.
Tldr; existing solutions are suitable for forensic analysis, whereas I'm
looking to solve the runtime analysis problem.
-bryan
[-- Attachment #2: Type: text/html, Size: 1448 bytes --]
next prev parent reply other threads:[~2014-12-04 16:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 8:41 [Qemu-devel] [PATCH 0/1] qmp: extend QMP to provide read/write access to physical memory Bryan D. Payne
2014-11-26 8:41 ` [Qemu-devel] [PATCH 1/1] " Bryan D. Payne
2014-11-26 15:16 ` Eric Blake
2014-11-26 20:27 ` [Qemu-devel] [PATCH v2] " Bryan D. Payne
2014-11-26 20:27 ` [Qemu-devel] [PATCH] " Bryan D. Payne
2014-11-27 2:04 ` Fam Zheng
2014-12-04 3:37 ` Bryan D. Payne
2014-12-04 4:57 ` Fam Zheng
2014-12-04 6:28 ` Bryan D. Payne
2014-12-04 7:38 ` Fam Zheng
2014-12-04 16:43 ` Bryan D. Payne
2014-12-05 1:20 ` Fam Zheng
2014-12-04 9:08 ` Markus Armbruster
2014-12-04 16:49 ` Bryan D. Payne [this message]
2014-12-05 8:44 ` Markus Armbruster
2014-12-05 21:25 ` Bryan D. Payne
2014-12-08 15:06 ` Markus Armbruster
2014-12-09 15:12 ` Bryan D. Payne
2014-12-11 3:33 ` Bryan D. Payne
2014-12-11 5:45 ` Fam Zheng
2014-12-11 6:07 ` Bryan D. Payne
2014-12-12 2:28 ` Bryan D. Payne
2014-12-12 3:29 ` Fam Zheng
2014-12-01 22:10 ` Eric Blake
2014-12-03 23:07 ` Bryan D. Payne
2014-12-04 15:08 ` Eric Blake
2014-12-04 16:50 ` Bryan D. Payne
2014-12-04 18:40 ` Bryan D. Payne
2014-12-04 22:43 ` Eric Blake
2014-12-01 22:12 ` [Qemu-devel] [PATCH v2] " Eric Blake
2014-12-02 4:36 ` Bryan D. Payne
2014-12-02 5:26 ` Fam Zheng
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='CAFpPvXC2AzXrqw3_t5+T721gp=5kF+3DAT-2Eda9kPWyjtdP=Q@mail.gmail.com' \
--to=bdpayne@acm.org \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).