From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] how to monitor memery access upon QEMU
Date: Sat, 8 Nov 2008 18:57:10 +0000 [thread overview]
Message-ID: <20081108185710.GA14050@miranda.arrow> (raw)
In-Reply-To: <f284c33d0811080650o2346b2efm6ce711af40ec07fb@mail.gmail.com>
On Sat, Nov 08, 2008 at 09:50:39PM +0700, Mulyadi Santosa wrote:
> probably this doesn't directly answer your question, but you may check
> http://www.few.vu.nl/argos/. In short, it's a project to capture every
> register, memory and I/O access. The main goal is to analyze zero day
> attack, but I believe it could serve another goal as well..
Hrm, I wonder if it'd be possible to use a modified QEMU to avoid
problems such as the recent Linux ftrace bug (i.e. the bug that bricked
a number of Intel e1000e cards).
(Or perhaps that sort of testing is nothing new...)
--
Stuart Brady
next prev parent reply other threads:[~2008-11-08 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 0:31 [Qemu-devel] how to monitor memery access upon QEMU LIU Limin
2008-11-08 14:50 ` Mulyadi Santosa
2008-11-08 14:53 ` LIU Limin
2008-11-08 18:57 ` Stuart Brady [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-07 12:08 LIU Limin
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=20081108185710.GA14050@miranda.arrow \
--to=sdbrady@ntlworld.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).