From: David Woodhouse <dwmw2@infradead.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Impractical ideas?
Date: Fri, 07 May 2004 10:44:20 +0100 [thread overview]
Message-ID: <1083923060.4526.186.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <c7dnul$vto$1@sea.gmane.org>
On Thu, 2004-05-06 at 17:08 +0100, Robert Wittams wrote:
> Hi,
>
> Having installed Win2k and various Linuxes under qemu, I've got all excited
> at the potential of this project, and have been entertaining all kinds of
> possibly impractical ideas...
>
> I was wondering if anyone had thought of using Qemu + a special kernel
> module to do reverse engineering of binary or windows only drivers.
>
> I'm not sure if I'm missing something really obvious, but it seems like the
> following should be possible:
>
> Run a virtual machine in qemu with, for example, the binary nvidia drivers
> on a linux system. On the host, a kernel module is configured that can
> perform any operations on the hardware that are necessary (io writes and
> dma, etc) and report interrupts to qemu.
Someone was muttering the other day about the possibility of putting
qemu in the kernel and using it to run i386 binary-only modules in
non-i386 host kernels.
I think it's a sick idea, but I might look at it anyway. After all, it's
no worse than running the ACPI crap in an interpreter.
--
dwmw2
next prev parent reply other threads:[~2004-05-07 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 16:08 [Qemu-devel] Impractical ideas? Robert Wittams
2004-05-06 18:06 ` John R. Hogerhuis
2004-05-06 21:52 ` J. Mayer
2004-05-06 22:11 ` John R. Hogerhuis
2004-05-07 1:34 ` Jason Gress
2004-05-07 1:38 ` John R. Hogerhuis
2004-05-07 9:44 ` David Woodhouse [this message]
2004-05-07 17:13 ` Irvin Probst
2004-05-07 17:51 ` Chad Page
2004-05-07 19:21 ` David Woodhouse
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=1083923060.4526.186.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--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).