From: Nicolas Pitre <nico@cam.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: mingo@elte.hu, tglx@linutronix.de, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -rt 2/2] arm update
Date: Thu, 18 May 2006 09:53:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605180947180.18071@localhost.localdomain> (raw)
In-Reply-To: <200605141557.k4EFv5Sd004979@dwalker1.mvista.com>
> - adds a new NR_syscalls macro, converts the old one into __NR_syscalls for
> calculating the table padding .
Why?
> --- linux-2.6.16.orig/arch/arm/kernel/entry-common.S
> +++ linux-2.6.16/arch/arm/kernel/entry-common.S
> @@ -90,8 +90,8 @@ ENTRY(ret_from_fork)
> b ret_slow_syscall
>
>
> - .equ NR_syscalls,0
> -#define CALL(x) .equ NR_syscalls,NR_syscalls+1
> + .equ __NR_syscalls,0 @ Used to determine syscall table padding.
> +#define CALL(x) .equ __NR_syscalls,__NR_syscalls+1
> #include "calls.S"
> #undef CALL
> #define CALL(x) .long x
> @@ -205,7 +205,7 @@ ENTRY(vector_swi)
> tst ip, #_TIF_SYSCALL_TRACE @ are we tracing syscalls?
> bne __sys_trace
>
> - cmp scno, #NR_syscalls @ check upper syscall limit
> + cmp scno, #__NR_syscalls @ check upper syscall limit
[...]
Please get rid of those changes.
> --- linux-2.6.16.orig/include/asm-arm/unistd.h
> +++ linux-2.6.16/include/asm-arm/unistd.h
> @@ -361,6 +361,9 @@
> #define __NR_get_mempolicy (__NR_SYSCALL_BASE+320)
> #define __NR_set_mempolicy (__NR_SYSCALL_BASE+321)
>
> +// FIXME: check this number ...
> +#define NR_syscalls 322
> +
> /*
> * The following SWIs are ARM private.
> */
> @@ -534,9 +537,6 @@ type name(type1 arg1, type2 arg2, type3
> #define __ARCH_WANT_SYS_SOCKETCALL
> #endif
>
> -// FIXME: check this number ...
> -#define NR_syscalls 328
> -
> #endif
>
> #ifdef __KERNEL_SYSCALLS__
And no NR_syscalls definition should be present in asm-arm/unistd.h at
all.
Nicolas
next prev parent reply other threads:[~2006-05-18 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 15:57 Daniel Walker
2006-05-18 8:06 ` Ingo Molnar
2006-05-18 13:53 ` Nicolas Pitre [this message]
2006-05-18 14:27 ` Daniel Walker
2006-05-18 15:26 ` Nicolas Pitre
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=Pine.LNX.4.64.0605180947180.18071@localhost.localdomain \
--to=nico@cam.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®