DragonFly kernel List (threaded) for 2003-07
Re: syscall messaging interface API
In article <200307231926.h6NJQppi038541@xxxxxxxxxxxxxxxxxxxx>,
Matthew Dillon wrote:
> Here is my idea for the system messaging interface. I will use a
> new trap gate (0x81) to implement it, because it occurs to me that
> a message interface really ought to pass and return information in
> registers rather then on the stack (since the message itself is already
> in user memory we might as well just have to do the copyin() on the
> contents rather then on both the system messaging interface arguments
> and the contents of the message). And a new trap gate isolates us from
> the old syscall mechanism.
> int 0x81 to dispatch, arguments in eax, ecx, edx, return value in eax.
How will that affect optimisation w/ the limited register set on ia32?
Adrian Chadd <angryskul> learning is bad
<adrian@xxxxxxxxxxx> <angryskul> it just makes the people around you dumber
(angryskul == alfred@irc) <angryskul> :(