From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] question about syscall
Date: Sun, 8 Feb 2009 00:33:29 +0700 [thread overview]
Message-ID: <f284c33d0902070933k5e10ec40k362dcd8d6b88d3a@mail.gmail.com> (raw)
In-Reply-To: <dec4146b0902070515y1d447578o6e5ffc29615ecf4d@mail.gmail.com>
Hi
On Sat, Feb 7, 2009 at 8:15 PM, Antonio Ricci <ricciantonio@gmail.com> wrote:
> Hi all,
> i'd want to understand how Qemu handles system calls while executing both
> Linux and Windows operating system. I've searched on the web with no
> results.
> Do you know if there is some documentation about syscall handling in Qemu?
> Thanks in advance for help
I assume you ask about full system emulation. Try to check how Qemu
intercept int 80h or SYSENTER/SYSCALL instruction (if the guest OS is
Linux). Not sure what Windows does when doing system call, maybe by
executing int instruction toward certain vectors too.
As usual, related interrupt handler will be executed (and translated).
So from Qemu point of view, it's strictly a matter of intercepting
code and translating it. It's the guest OS that does the real work on
syscall handling.
In user space emulation only, system call is intercepted by the normal
dynamic code translation, but syscall is handled by syscall() C
function. The complication could arise if the guest OS is not the same
type as the host OS. Some "interpretations" are needed here.
regards,
Mulyadi.
next prev parent reply other threads:[~2009-02-07 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 13:15 [Qemu-devel] question about syscall Antonio Ricci
2009-02-07 13:27 ` Lionel Landwerlin
2009-02-07 17:33 ` Mulyadi Santosa [this message]
2009-02-09 19:23 ` Antonio Ricci
2009-02-11 6:25 ` Mulyadi Santosa
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=f284c33d0902070933k5e10ec40k362dcd8d6b88d3a@mail.gmail.com \
--to=mulyadi.santosa@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).