qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.landwerlin@openwide.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] question about syscall
Date: Sat, 07 Feb 2009 14:27:43 +0100	[thread overview]
Message-ID: <1234013263.13547.3.camel@cocoduo.atr> (raw)
In-Reply-To: <dec4146b0902070515y1d447578o6e5ffc29615ecf4d@mail.gmail.com>

Le samedi 07 février 2009 à 14:15 +0100, Antonio Ricci a écrit :
> Hi all, 
> 
> 
> i'd want to understand how Qemu handles system calls while executing
> both Linux and Windows operating system.

A syscall is usually done by generating a cpu exception. In Qemu, when a
such exception is catched by a virtual cpu, Qemu executes the related
syscall (syscall number is usually put in a register). All of this
depends on the ABI.


-- 
Lione Landwerlin                                         

O p e n W i d e                    14, rue Gaillon 75002 Paris

  reply	other threads:[~2009-02-07 13:27 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 [this message]
2009-02-07 17:33 ` Mulyadi Santosa
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=1234013263.13547.3.camel@cocoduo.atr \
    --to=lionel.landwerlin@openwide.fr \
    --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).