From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Avi Kivity" <avi@qumranet.com>
Cc: "Pekka Paalanen" <pq@iki.fi>,
linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
"Christoph Hellwig" <hch@infradead.org>,
"Arjan van de Ven" <arjan@infradead.org>,
"Pavel Roskin" <proski@gnu.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
vegard.nossum@gmail.com
Subject: Re: mmiotrace bug: recursive probe hit
Date: Sat, 5 Apr 2008 10:40:18 +0300 [thread overview]
Message-ID: <84144f020804050040r6fd8b9a8h6d344b4ea53cb3e5@mail.gmail.com> (raw)
In-Reply-To: <47F72C12.9020701@qumranet.com>
On Sat, Apr 5, 2008 at 10:36 AM, Avi Kivity <avi@qumranet.com> wrote:
> It should not be too difficult to modify x86_emulate.c to do everything
> through a function vector. However there is a simpler (for you) solution:
> run the driver-to-be-reverse-engineered in a kvm guest, and modify kvm
> userspace to log accesses to mmio regions. This requires the not-yet-merged
> pci passthrough support. You can reverse engineer Windows drivers with this
> as well.
>
> This won't work for kmemcheck smp though.
For kmemcheck, I'd prefer the per-CPU page tables suggested by Ingo.
I'm having hard time understanding why that's a "ugly hack" compared
to using kvm for this...
next prev parent reply other threads:[~2008-04-05 7:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 14:40 [RFC] mmiotrace full patch, preview 2 Pekka Paalanen
2008-03-09 14:46 ` Pekka Paalanen
2008-03-27 23:13 ` Vegard Nossum
2008-03-28 18:24 ` Pekka Paalanen
2008-03-28 20:25 ` mmiotrace bug: recursive probe hit Pekka Paalanen
2008-03-30 17:26 ` Pekka Paalanen
2008-04-03 21:07 ` Pekka Paalanen
2008-04-03 21:40 ` Vegard Nossum
2008-04-04 13:18 ` Pekka Paalanen
2008-04-05 7:36 ` Avi Kivity
2008-04-05 7:40 ` Pekka Enberg [this message]
2008-04-05 12:39 ` Avi Kivity
2008-04-05 15:58 ` Avi Kivity
2008-04-06 17:32 ` Pekka Paalanen
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=84144f020804050040r6fd8b9a8h6d344b4ea53cb3e5@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=avi@qumranet.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pq@iki.fi \
--cc=proski@gnu.org \
--cc=rostedt@goodmis.org \
--cc=vegard.nossum@gmail.com \
/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
all inboxes | Powered by JetHome®