From: amateur <tianlei.zhao@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ISA Proxy - possible?
Date: Wed, 20 Jun 2007 09:46:15 +0800 [thread overview]
Message-ID: <20070620014615.GA4518@163.com> (raw)
In-Reply-To: <200706191401.51064.daniel@schwen.de>
On Tue, Jun 19, 2007 at 02:01:50PM +0200, Daniel Schwen wrote:
> Would it be possible to register a set of io ports and io memory locations
> with qemu and have all read write operations passed on to the host system?
>
> A quick look at the source shows me the two look-up tables
> IOPortReadFunc *ioport_read_table[3][MAX_IOPORTS];
> IOPortWriteFunc *ioport_write_table[3][MAX_IOPORTS];
> Instead of the default function (which just generates debug output) it should
> be possible to register functions which call the ioport read/write commands
> on the host system (qemu would have to be launched as root to acquire io
> permissions).
>
> Same should work with io memory using the cpu_register_io_memory function.
> Or am I far off base?
>
> Reason is that I'd like to emulate some very old linux installations which
> access custom ISA hardware. For some of the ISA boards we have no source
> code, only binaries linked to a 2.0.something kernel...
-------------------------
I think it is possible just as you said. But, take care of the
interrupts! If your device don't generate interrupts, that's fine! If
they do, then you must find a way to propagate this interrupt signal
to qemu.
And, there can't be another entity(e.g, host driver) operating on the
device simultaneously.
--
You worry too much about your job. Stop it. You are not paid enough to worry.
prev parent reply other threads:[~2007-06-20 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 12:01 [Qemu-devel] ISA Proxy - possible? Daniel Schwen
2007-06-20 1:46 ` amateur [this message]
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=20070620014615.GA4518@163.com \
--to=tianlei.zhao@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.