From: win <xuwh06@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Question] How KQEMU works together with QEMU
Date: Mon, 7 Dec 2009 18:56:51 -0800 [thread overview]
Message-ID: <43be52050912071856k8082afwb7dec1ce49667abe@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi, everybody,
I am a newbie to QEMU and have been reading the QEMU code for nearly one
month. I got a picture of how QEMU works, but still cannot figure out how
KQEMU works together with QEMU. Could you give me some clues to the
following questions?
1) The interrupts in QEMU are driven by the SIGALRM and SIGIO signal, in
whose signal handlers the cpu chain is reset and then the interrupts could
be checked in the main loop. However, when executing code directly on the
hardware using KQEMU, how to stop the code execution and check the
interrupts?
2) As far as I know, KQEMU would change the IDT to hook some its own
interrupt handlers. But in detail, what interrupt handlers are hooked? Is
the timer interrupt handler included? How to restore the host's handler back
to the IDT when KQEMU needs to be switched out?
Thanks! I appreciate for your help.
cheers,
peter
[-- Attachment #2: Type: text/html, Size: 943 bytes --]
reply other threads:[~2009-12-08 2:56 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=43be52050912071856k8082afwb7dec1ce49667abe@mail.gmail.com \
--to=xuwh06@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).