From: Arnd Bergmann <arnd@arndb.de>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxram@us.ibm.com, leitao@debian.org,
Boqun Feng <boqun.feng@gmail.com>,
gregkh <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH 2/3] powerpc: Add system call table generation support
Date: Mon, 24 Sep 2018 22:59:59 +0200 [thread overview]
Message-ID: <CAK8P3a2hi-Ndh7X-9r3NhBUJXQBTBFsTU==GbHesy6YD9idCJA@mail.gmail.com> (raw)
In-Reply-To: <CALxhOngVYQRwbcUg6c_3LcKAEoBwyN1B478LqRGmWEGL004--w@mail.gmail.com>
On Tue, Sep 18, 2018 at 2:15 PM Firoz Khan <firoz.khan@linaro.org> wrote:
>
> On 14 September 2018 at 15:31, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Fri, Sep 14, 2018 at 10:33 AM Firoz Khan <firoz.khan@linaro.org> wrote:
> >
> >> ---
> >> arch/powerpc/kernel/syscalls/Makefile | 51 ++++
> >> arch/powerpc/kernel/syscalls/syscall_32.tbl | 378 ++++++++++++++++++++++++++++
> >> arch/powerpc/kernel/syscalls/syscall_64.tbl | 372 +++++++++++++++++++++++++++
> >> arch/powerpc/kernel/syscalls/syscallhdr.sh | 37 +++
> >> arch/powerpc/kernel/syscalls/syscalltbl.sh | 38 +++
> >
> > I think you should only need a single .tbl input file here.
>
> Yes, we can do that way also.As I mentioned, it will add
> more complexity in the script.
>
> The script has to be smart enough to parse the
> .tbl if we add more thing in the .tble file. It need more
> logic in the scripts. This is not common. So if you keep
> separate .tbl we can avoid this.
But all three existing architectures (x86, s390 and arm) already
have the capability to parse the table and generate different output
from that.
> ABI flag is serving *nothing* in all other architecture including
> SPARC.
If you don't use it in sparc, I think that's a bug, see e.g.
#ifdef __32bit_syscall_numbers__
#define __NR_setresuid32 108 /* Linux Specific, sigvec under
SunOS */
#else
#define __NR_setresuid 108 /* Linux Specific, sigvec under
SunOS */
#endif
> But as I told in the cover letter, I followed x86/arm/
> s390 architecture's system table generation implementation.
> They are keeping ABI flag. In our case we can delete this
> flag completely from all architectures.
>
> Most of the architecture these 32/64 similarity is absent.
> So it would be better keep separate files to maintain a
> generic script across all architecture.
There are a couple of architectures that definitely need it:
ARM for oabi, x86 for x32, s390, parisc and sparc for compat,
asm-generic for compat, powerpc for compat and spu,
and arm64 if we want to share the arm32 syscall table
for compat mode later.
Arnd
next prev parent reply other threads:[~2018-09-24 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:32 [PATCH 0/3] System call table generation support Firoz Khan
2018-09-14 8:32 ` Firoz Khan
2018-09-14 8:32 ` [PATCH 1/3] powerpc: Replace NR_syscalls macro from asm/unistd.h Firoz Khan
2018-09-14 8:32 ` Firoz Khan
2018-09-14 8:32 ` [PATCH 2/3] powerpc: Add system call table generation support Firoz Khan
2018-09-14 8:32 ` Firoz Khan
2018-09-14 10:01 ` Arnd Bergmann
2018-09-14 10:01 ` Arnd Bergmann
2018-09-18 12:15 ` Firoz Khan
2018-09-18 12:15 ` Firoz Khan
2018-09-24 20:59 ` Arnd Bergmann [this message]
2018-09-24 20:59 ` Arnd Bergmann
2018-09-25 0:48 ` Michael Ellerman
2018-09-25 0:48 ` Michael Ellerman
2018-09-25 6:00 ` Arnd Bergmann
2018-09-25 6:00 ` Arnd Bergmann
2018-09-25 12:25 ` Michael Ellerman
2018-09-25 12:25 ` Michael Ellerman
2018-09-14 8:33 ` [PATCH 3/3] powerpc: uapi header and system call table file generation Firoz Khan
2018-09-14 8:33 ` Firoz Khan
2018-11-29 6:34 ` [PATCH 0/3] System call table generation support Satheesh Rajendran
2018-11-29 8:18 ` Firoz Khan
2018-11-29 8:18 ` Firoz Khan
2018-11-30 7:01 ` Satheesh Rajendran
2018-11-30 7:01 ` Satheesh Rajendran
2018-11-30 9:40 ` Firoz Khan
2018-11-30 9:40 ` Firoz Khan
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='CAK8P3a2hi-Ndh7X-9r3NhBUJXQBTBFsTU==GbHesy6YD9idCJA@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=leitao@debian.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).