> Task wants to do a syscall (i.e. int 0x30 in Fiasco), the kernel
> process tracing the task sees the signal in its SIGCHLD handler. It
> pulls the registers out of the task's address space using
> PTRACE_GETREGS and sets up an interrupt frame on the kernel stack.
Hmmm, I would have the kernel process let the system call bump it out of
wait() rather than delivering a SIGCHLD. And, I'd be inclined to lomgjmp
over to the kernel stack.
Or, even better, have it already running on the appropriate kernel stack,
so it can just read the system call from PTRACE_GETREGS and call into the
Similarly, with other signals, like the timer, SIGIO, or page faults, it
would just annull the signal and call into the IRQ system. Although page
faults will be difficult because of the inability to read err or cr3, as
you've pointed out.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:29 EST