From: Heli <helicoterus-elih@yahoo.it>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How does a system call work on QEMU?
Date: Thu, 14 May 2009 15:10:37 +0200 [thread overview]
Message-ID: <4A0C184D.3030307@yahoo.it> (raw)
In-Reply-To: <200905141119.01914.paul@codesourcery.com>
Paul Brook wrote:
> On Thursday 14 May 2009, helicoterus-elih@yahoo.it wrote:
> > > Which mode of Qemu operations do you refer to? if you refer to full
> > > MMU emulation (no KVM or kqemu involved then), then intercepting
> > > syscall is basically intercepting interrupt 80 hex or SYSENTER/SYSCALL
> > > into host user mode instruction during code translation.
> >
> > Ok, I refer to full emulation.
> > When QEMU intercepts a system call what does it do? What type of
> > translation or modification does it perform?
>
>
> It does exactly the same as real hardware.
>
>
> Paul
>
>
Does QEMU generate a system call that goes to libc library and the to
the kernel?
Then the kernel run it on hardware, kernel replies to libc and libc
notifies to QEMU. QEMU replies to guest O.S, is it true?
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
next prev parent reply other threads:[~2009-05-14 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 6:50 [Qemu-devel] How does a system call work on QEMU? helicoterus-elih
2009-05-14 10:19 ` Paul Brook
2009-05-14 13:10 ` Heli [this message]
2009-05-14 16:40 ` Avi Kivity
2009-05-14 17:11 ` grisu46
2009-05-14 17:48 ` Avi Kivity
2009-05-14 18:00 ` grisu46
2009-05-15 4:49 ` Glauber Costa
2009-05-17 8:46 ` Heli
2009-05-17 9:31 ` Avi Kivity
2009-05-17 14:41 ` Fernando Carrijo
2009-05-14 14:57 ` Mulyadi Santosa
-- strict thread matches above, loose matches on Subject: below --
2009-05-15 8:54 helicoterus-elih
2009-05-13 18:41 helicoterus-elih
2009-05-14 4:38 ` 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=4A0C184D.3030307@yahoo.it \
--to=helicoterus-elih@yahoo.it \
--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).