From: Jong Chun Park <joumon@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] System call from a Guest Linux
Date: Wed, 3 Feb 2010 11:03:59 -0700 [thread overview]
Message-ID: <2e320c2d1002031003i36bc3848hbb4b030a6dfd4156@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Hi, all?
First of all, I apologize you for this spam. I'm working with QEMU v0.12.1
with i386 Linux guest on x86-64 Linux host. I'm trying to find a point in
the source code where a system call from the guest OS is handled. If I'm not
mistaken, QEMU disassembles an instruction of INT # in a switch statement of
target-i386/translate.c and then calls helper_sysenter of
target-i386/op_helper.c. The problem is how to tell difference between a
system call of the guest OS and a system call of QEMU (I'm not sure of this,
though). Assume the following code is executed after compilation in the
guest OS:
int main() {
if (access("hello.txt", R_OK)!=0) {
[-- Attachment #2: Type: text/html, Size: 759 bytes --]
next reply other threads:[~2010-02-03 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 18:03 Jong Chun Park [this message]
2010-02-03 18:08 ` [Qemu-devel] [Please discard the previous mail] System call from a Guest Linux Jong Chun Park
2010-02-03 19: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=2e320c2d1002031003i36bc3848hbb4b030a6dfd4156@mail.gmail.com \
--to=joumon@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).