RE: task_ops?

Noel Burton-Krahn (noel@harleystreet.com)
Tue, 6 Jan 1998 10:24:55 -0800


> The obvious question is why ?
>
> Firstly tasks dont get interrupts they just go off whenever they arrive.
>
> Item #2 - syscalls is easy - you can create new personalities and have them
> behave differently - but you will have to sort the traps/lcalls in entry.S
>
> Alan
>
>

I'm making something like a binary emulator which will execute
assembly instructions in user space, but handle signals and syscalls
differently than other native Linux tasks.

At first I thought I could just write another personality with a new
exec_domain, but after looking at execdomain.c and entry.S I'm not
sure. entry.S has entries for both lcall7 and syscall. There's only
one lcall7 function defined in the kernel, and that sends SEGV.

What are the semantics of an lcall7 handler and what's the difference
between lcall7 and syscall? Perhaps there should be another entry in
exec_domain for a syscall handler?

--Noel