From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Who call I/O cpu_in*/cpu_out*?
Date: Thu, 3 Aug 2006 18:29:41 +0200 [thread overview]
Message-ID: <b921df970608030929p39032dfg2d2602ac3257b815@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
Hello,
This is what I understand:
In vl.c code:
-In qemu initialization will be create and initialize a table in which there
are I/O read/write function corresponding to I/O address.
-When emulated devices are inizialited they register IO function in this
table, in this way it can be called when an instruction want to access at
this address-device right?
-These function are called by cpu_write{b|w|l} in case of byte/word/long.
I suppose when there is an instruction op-code regards IO there is a
mechanism that calls these function. Can you say me where it does this?
Thank you
Ale
[-- Attachment #2: Type: text/html, Size: 628 bytes --]
reply other threads:[~2006-08-03 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b921df970608030929p39032dfg2d2602ac3257b815@mail.gmail.com \
--to=ale.corradi@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 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).