Xref: utzoo comp.sys.encore:457 comp.os.mach:182
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!sun-barr!ccut!titcca!kddlab!icot32!isvax!uemura
From: uemura@isvax.isl.melco.co.jp (Joe Uemura)
Newsgroups: comp.sys.encore,comp.os.mach
Subject: Mach threads syscalls (In English)
Keywords: Mach, threads
Message-ID: <2337@isvax.isl.melco.co.jp>
Date: 14 Dec 89 08:46:09 GMT
Organization: Mitsubishi Electric, Kamakura, Japan
Lines: 17


I've been experimenting with Mach threads (not Cthreads)  on  our
Encore  running  Mach  0.5.  After  poking around several include
files, I was able to get a thread created and got it  running  by
following the hints presented in the "Mach Kernel Interface Manu-
al". Since most of what I did was guess work, I am looking for  a
more  detailed  explanation of how Mach threads syscalls actually
work, specially how much of the thread  state  I  should  provide
through  the set state syscall. I'm interested in both the syntax
as well as the semantics of the threads syscalls. I would  appre-
ciate  any pointers to documents, tech reports, actual code exam-
ples, anything. I believe I have read most of the CMU Mach papers
but  since  threads  calls  are machine dependent, I haven't been
able to find much specific (Encore/NS32K) information  concerning
the calls.

Please email responses to me.