From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: sys_syscall patch.
Date: Mon, 24 Jun 2002 12:46:41 +0200 [thread overview]
Message-ID: <3D16F891.78A333BA@mips.com> (raw)
In-Reply-To: 20020624122450.A25659@dea.linux-mips.net
Ralf Baechle wrote:
> 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 ...
/sbin/rpc.lockd.
It use syscall() to indirectly call the 'sys_nfsservctl' syscall, why it
doesn't do the syscall directly is beyond me.
>
> 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
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2002-06-24 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 9:07 sys_syscall patch Carsten Langgaard
2002-06-24 9:54 ` Ralf Baechle
2002-06-24 10:06 ` Carsten Langgaard
2002-06-24 10:24 ` Ralf Baechle
2002-06-24 10:46 ` Carsten Langgaard [this message]
2002-06-24 11:38 ` Maciej W. Rozycki
2002-06-24 11:45 ` Ralf Baechle
2002-06-24 14:49 ` Maciej W. Rozycki
2002-06-24 12:02 ` Kevin D. Kissell
2002-06-24 12:02 ` Kevin D. Kissell
2002-06-24 12:04 ` Ralf Baechle
2002-06-24 12:02 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D16F891.78A333BA@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.