From: kuas <ku4s@users.sourceforge.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] System Call Mechanism
Date: Thu, 19 Feb 2004 16:30:46 -0500 [thread overview]
Message-ID: <40352B06.3030406@users.sourceforge.net> (raw)
Hello,
I'm posting this question to here since this is development problem, the
other newsgroup seems to be more like users problem and I would think
this forum would be able to explain more about my question. I will post
to the other newsgroup if that's the one where I should really be posting
I'm trying to find out how the system call mechanism presently works in
UML. I have looked into the high level description in the slides. Any
pointers to any other documents that I might missed are appreciated.
I seems to me the new or current implementation of system call involves
conversion from interupt 80 at the host OS into signals back in UML
kernel. Is this the same mechanism for the current TT and SKAS? Or TT
mode still using ptrace thread tracing mechanism to intercept the system
call? If there is a signal from the host to UML kernel process, there
must be a signal handler registered by the UML kernel.
Any quick deeper overview about this mechanism would be really welcome.
Thanks in advance.
Kuas.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&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 reply other threads:[~2004-02-19 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 21:30 kuas [this message]
2004-02-25 15:52 ` [uml-devel] System Call Mechanism BlaisorBlade
2004-02-28 2:29 ` Kuas
2004-02-29 12:26 ` BlaisorBlade
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=40352B06.3030406@users.sourceforge.net \
--to=ku4s@users.sourceforge.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.