David Woodhouse <dwmw2@infradead.org> wrote:
> We already handle doing iBCS and Solaris syscalls by trapping int 7 and
> int 0x27 insns and using a dedicated syscall handler - it doesn't go
> anywhere near the original Linux syscall table.
I was planning on having using a Linux syscall rather than an interrupt, since
the int ties it to i386.
> What method does Win32 use to execute syscalls? Would it be useful to trap
> that directly?
It does and it doesn't is the answer I think. NT/Win2000 certainly does
not... kernel32.dll renders the Win32 calls into "Native API" calls, which are
defined in ntdll.dll. These use "int 0x2e" to obtain access to the kernel, but
are mostly undocumented (typically).
As for Win95/98/ME, I would have thought these would implement the Win32
syscalls directly.
David Howells
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:15 EST