[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020804050040r6fd8b9a8h6d344b4ea53cb3e5@mail.gmail.com>
Date: Sat, 5 Apr 2008 10:40:18 +0300
From: "Pekka Enberg" <penberg@...helsinki.fi>
To: "Avi Kivity" <avi@...ranet.com>
Cc: "Pekka Paalanen" <pq@....fi>, linux-kernel@...r.kernel.org,
"Ingo Molnar" <mingo@...e.hu>,
"Christoph Hellwig" <hch@...radead.org>,
"Arjan van de Ven" <arjan@...radead.org>,
"Pavel Roskin" <proski@....org>,
"Steven Rostedt" <rostedt@...dmis.org>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>, vegard.nossum@...il.com
Subject: Re: mmiotrace bug: recursive probe hit
On Sat, Apr 5, 2008 at 10:36 AM, Avi Kivity <avi@...ranet.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...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists