[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <481E3433.2030408@zytor.com>
Date: Sun, 04 May 2008 15:09:55 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: monstr@...nam.cz
CC: Arnd Bergmann <arnd@...db.de>, microblaze-uclinux@...e.uq.edu.au,
Matthew Wilcox <matthew@....cx>,
Will Newton <will.newton@...il.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-arch@...r.kernel.org, git@...inx.com,
John Williams <john.williams@...alogix.com>,
Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
John Linn <John.Linn@...inx.com>
Subject: Re: microblaze syscall list
Michal Simek wrote:
> /* fs/select.c */
> .long sys_select /* obsolete -> sys_pselect6 */
> ok .long sys_pselect7
> .long sys_pselect6 /* obsolete -> sys_pselect7 */
I thought there was some semantic differences between select() and
pselect()... perhaps those changes have been removed?
>
> /* kernel/sys_ni.c */
> .long sys_ni_syscall /* :-) */
>
There is a school of thought that it's useful to reserve a system call
number (usually zero) as a system call that is *guaranteed* to have no
effect.
> /* arch - microblaze specific */
> /* arch/microblaze/kernel/signal.c */
> .long sys_sigreturn /* obsolete -> sys_rt_sigreturn */
> ok .long sys_rt_sigreturn_wrapper /*.long sys_rt_sigreturn*/
> .long sys_sigaction /* obsolete -> rt_sigaction */
> .long sys_sigsuspend /* obsolete -> rt_sigsuspend */
Btw, please implement rt_sigreturn sanely; on x86, for example, one has
to pop a word off the stack before one can invoke the system call, when
used as sa_restorer...
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists