Re: [parisc-linux] Re: how to handle ERESTART_RESTARTBLOCK ?

[Carlos O'Donell <carlos@baldric.uwo.ca>]

On Sun, Oct 26, 2003 at 12:37:51AM -0700, Randolph Chung wrote:
> here's a patch that implements the required logic. probably can be
> improved some.... comments appreciated.
> 
> About __NR_restart_syscall, some archs use syscall #0 (unused for pa
> afaict), others define a new syscall number. Any preferences? If it's
> zero then i think i will remove the reassemble_14 logic.

I don't see why #0 can't be used here. Then again, why can't you code
the syscall number directly into the hex? Are you expecting it to
change? :)

> +		if (regs->gr[28] == -ERESTART_RESTARTBLOCK) {
> +			unsigned int *usp = (unsigned int *)regs->gr[30];
> +
> +			/* Setup a trampoline to restart the syscall
> +			 * with __NR_restart_syscall
> +			 *
> +			 *  0: ble 0x100(%%sr2, %%r0)
> +			 *  4: ldi __NR_restart_syscall, %r20
> +			 *  8: b,l .+8, %r21
> +			 * 12: depi 0,31,2,%r21
> +			 * 16: ldw 16(%r21), %rp
> +			 * 20: bv %r0(%rp)
> +			 * 24: ldo -64(%sp), %sp

Adding stack here can be detremental to the userspace program. It's not
expecting you to have a stack, and it expects the syscall to live within 
its calling frame. When we setup the signal return trampoline we don't
mess with the stack either :) Though this context is different.

> +			 * 28: nop
> +			 * 32: <return address> (2 slots for 64-bit)
> +			 */

c.