From: Jeff Dike <jdike@addtoit.com>
To: Young Koh <young.koh@gmail.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Explaination of system call function flow in TT mode
Date: Mon, 16 May 2005 16:52:33 -0400 [thread overview]
Message-ID: <20050516205233.GA9668@ccure.user-mode-linux.org> (raw)
In-Reply-To: <3524bf1f05051611528eb7bc1@mail.gmail.com>
On Mon, May 16, 2005 at 02:52:37PM -0400, Young Koh wrote:
> Suppose the tracee attmpts to invoke a host system call. then, it will
> be intercepted by the tracer as in TT mode. (In TT mode, the tracer
> turns off tracing and sends SIGUSR2 to the tracee, and then, the
> signal handler in the tracee will execute the system call.) but, in
> SKAS mode, because the tracee doesn't have the UML kernel code, only
> the tracer knows about the system call code. The tracer cannot simply
> send a signal to make the tracee execute the system call. Then how
> does it do? Does the tracer execute the system call for the tracee?
The tracer is the kernel, so it just executes the system call.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-05-17 1:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003e01c503b3$f3e46cb0$ac655e0a@sha.st.com>
2005-01-28 19:10 ` [uml-devel] Explaination of system call function flow in TT mode Blaisorblade
2005-02-02 15:29 ` [uml-devel] " Alex LIU
2005-02-03 19:38 ` Blaisorblade
2005-05-16 14:08 ` [uml-devel] " Young Koh
2005-05-16 17:08 ` Blaisorblade
2005-05-16 18:52 ` Young Koh
2005-05-16 20:52 ` Jeff Dike [this message]
2005-05-16 21:24 ` Blaisorblade
2005-05-17 0:09 ` Young Koh
2005-05-17 0:17 ` Blaisorblade
2005-05-17 17:56 ` Young Koh
2005-05-17 22:00 ` Jeff Dike
2005-05-18 9:47 ` Bodo Stroesser
2005-05-18 13:24 ` Young Koh
2005-05-18 14:57 ` Blaisorblade
2005-05-18 15:09 ` Jeff Dike
2005-05-18 15:26 ` Bodo Stroesser
2005-05-18 15:03 ` Jeff Dike
2005-05-18 13:33 ` Jeff Dike
2005-05-18 15:20 ` Bodo Stroesser
2005-05-18 15:28 ` Blaisorblade
2006-02-09 22:08 ` Young Koh
2006-02-09 23:38 ` Jeff Dike
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=20050516205233.GA9668@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=young.koh@gmail.com \
/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