From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Hardware interrupts
Date: Mon, 17 Jul 2006 20:28:06 +0200 [thread overview]
Message-ID: <b921df970607171128l5f62523ep37195dc00b5b676c@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
<http://fabrice.bellard.free.fr/qemu/qemu-tech.html#TOC18>
<http://fabrice.bellard.free.fr/qemu/qemu-tech.html#TOC18>
Hi all,
In http://fabrice.bellard.free.fr/qemu/qemu-tech.html:
"In order to be faster, QEMU does not check at every basic block if an
hardware interrupt is pending. Instead, the user must asynchrously call a
specific function to tell that an interrupt is pending. This function resets
the chaining of the currently executing basic block. It ensures that the
execution will return soon in the main loop of the CPU emulator. Then the
main loop can test if the interrupt is pending and handle it."
What means "the user must asynchrously call a specific function..."?
In which sense "user must"?
Which "Specific function"?
How QEMU checks for hardware interrups?
Thanks
[-- Attachment #2: Type: text/html, Size: 1025 bytes --]
next reply other threads:[~2006-07-17 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 18:28 Alessandro Corradi [this message]
2006-07-17 18:44 ` [Qemu-devel] Hardware interrupts Paul Brook
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=b921df970607171128l5f62523ep37195dc00b5b676c@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).