| To: | Carsten Langgaard <carstenl@mips.com> |
|---|---|
| Subject: | Re: sys_syscall patch. |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Mon, 24 Jun 2002 12:24:50 +0200 |
| Cc: | linux-mips@oss.sgi.com |
| In-reply-to: | <3D16EF3C.BCCB020@mips.com>; from carstenl@mips.com on Mon, Jun 24, 2002 at 12:06:52PM +0200 |
| References: | <3D16E14C.5C8D2FAD@mips.com> <20020624115452.A25138@dea.linux-mips.net> <3D16EF3C.BCCB020@mips.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5.1i |
On Mon, Jun 24, 2002 at 12:06:52PM +0200, Carsten Langgaard wrote: > > At least it makes my system work as well as for the 32-bit kernel. What programs btw are using syscall()? To be honest I don't recall one ... Looking more into it I found a nice showstopper - a few functions like _sys_sigsuspend() expect a struct pt_regs on the stack. That's only working if we call those functions directly from the exception handler. It won't work if we have another function's stackframe - in this case sys_syscall()'s there also ... Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: sys_syscall patch., Carsten Langgaard |
|---|---|
| Next by Date: | Re: sys_syscall patch., Carsten Langgaard |
| Previous by Thread: | Re: sys_syscall patch., Carsten Langgaard |
| Next by Thread: | Re: sys_syscall patch., Carsten Langgaard |
| Indexes: | [Date] [Thread] [Top] [All Lists] |