From: "Bryan D. Payne" <bdpayne@acm.org>
To: qemu-devel@nongnu.org
Cc: "Bryan D. Payne" <bdpayne@acm.org>, lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH 0/1] qmp: extend QMP to provide read/write access to physical memory
Date: Wed, 26 Nov 2014 00:41:11 -0800 [thread overview]
Message-ID: <1416991272-10277-1-git-send-email-bdpayne@acm.org> (raw)
Summary:
This patch improves Qemu support for virtual machine introspection.
Background:
Virtual machine introspection (VMI) is a technique where one accesses the
memory of a (usually) paused guest. This access is typically used to perform
security checks, debugging, or malware analysis. The LibVMI project provides
and open source library that simplifies VMI programming. LibVMI supports
both Xen and KVM environments.
Under KVM, LibVMI can work on systems today (albeit slowly) using the human
monitor command functionality to extract memory with the xp command. This
access is too slow for performance sensitive applications, so the LibVMI
project has created and maintained a QEMU patch that enables faster access.
We have used this patch for about 3 years now and it appears to be working
nicely for our community.
The patch in this email is an updated version of the LibVMI patch that aims
to conform to the Qemu coding guidelines. It is my hope that we can include
this in Qemu so that LibVMI users can leverage this faster access without
needing to do custom Qemu builds on their KVM systems.
Bryan D. Payne (1):
qmp: extend QMP to provide read/write access to physical memory
Makefile.target | 2 +-
memory-access.c | 200 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
memory-access.h | 11 ++++
monitor.c | 10 +++
qmp-commands.hx | 27 ++++++++
5 files changed, 249 insertions(+), 1 deletion(-)
create mode 100644 memory-access.c
create mode 100644 memory-access.h
--
1.9.1
next reply other threads:[~2014-11-26 8:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 8:41 Bryan D. Payne [this message]
2014-11-26 8:41 ` [Qemu-devel] [PATCH 1/1] qmp: extend QMP to provide read/write access to physical memory 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
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=1416991272-10277-1-git-send-email-bdpayne@acm.org \
--to=bdpayne@acm.org \
--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).