From: Glauber Costa <glommer@gmail.com>
To: grisu46 <grisu46@yahoo.it>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How does a system call work on QEMU?
Date: Fri, 15 May 2009 01:49:14 -0300 [thread overview]
Message-ID: <5d6222a80905142149v18af9aa3jf30ba0cfd3363d26@mail.gmail.com> (raw)
In-Reply-To: <4A0C5C48.6010700@yahoo.it>
On Thu, May 14, 2009 at 3:00 PM, grisu46 <grisu46@yahoo.it> wrote:
> Avi Kivity ha scritto:
>>
>> grisu46 wrote:
>>>>
>>>> No. Look at target-i386/translate.c, case 0x105 for syscall emulation.
>>>> Eventually it ends up calling helper_syscall().
>>>>
>>>
>>> Simplify?
>>> I am a newbie.
>>
>> Sorry, you're on your own. I can give you pointers but it's up to you to
>> follow them. If you're serious about understanding qemu you should be
>> prepared a lot of time reading the source code and processor documentation.
>>
> I would like to know how a virtualization program can perform a sensitive
> but not privileged operation. I learn about Xen and I like to understand (no
> deep details need) differences between Xen paravirtualization and QEMU
> emulator.
>
As the name suggests, qemu (in this case) is a processor _emulator_. You're not
doing any kind of sensitive operations on your host processor here.
You are emulating
a processor, an all state change happens in the emulated processor.
* qemu reads the instruction.
* qemu updates its internal state accordingly.
* qemu reads next instruction.
No big secret here.
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2009-05-15 4:49 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
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 [this message]
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=5d6222a80905142149v18af9aa3jf30ba0cfd3363d26@mail.gmail.com \
--to=glommer@gmail.com \
--cc=avi@redhat.com \
--cc=grisu46@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).