From: "Arnd Bergmann" <arnd@arndb.de>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: linux-kernel@vger.kernel.org,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
linux-kbuild@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [PATCH RFC v3 2/8] syscalls: Create unified partial table for all archs
Date: Mon, 10 Aug 2026 16:22:48 +0200 [thread overview]
Message-ID: <3ee5b6f6-8d71-4a01-bd50-3768ddb02b4a@app.fastmail.com> (raw)
In-Reply-To: <099046ab-ca4d-4a1e-97ad-e2fe05b9e81b@igalia.com>
On Mon, Aug 10, 2026, at 15:19, André Almeida wrote:
> Em 07/08/2026 17:40, Arnd Bergmann escreveu:
>>
>> I don't see the purpose of this and would prefer to not add that
>> extra option if the scripts works fine without it.
>>
>
> Some archs don't define __SYSCALL_WITH_COMPAT() (see x86_64 for
> instance), so that's why I have added this option. But I can define
> __SYSCALL_WITH_COMPAT() as SYSCALL(nr, native) for those archs.
Yes, I think that is the best solution here, yes. We certainly need
to use the compat version for .tbl files that only have one entry
but do use the compat ones (mips n32, arm64 aarch32), and using it
everywhere helps remove another special case here.
Side note: in the long run, I would hope we can remove those
intermediate macros entirely and just output a readable version
of the switch/case style top-level function that x86 generates
from the table.
Arnd
next prev parent reply other threads:[~2026-08-10 14:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 19:34 [PATCH RFC v3 0/8] syscalls: Add a shared " André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 1/8] syscalls: Make --abis parsing more robust André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 2/8] syscalls: Create unified partial table for all archs André Almeida
2026-08-07 20:40 ` Arnd Bergmann
2026-08-10 13:19 ` André Almeida
2026-08-10 14:22 ` Arnd Bergmann [this message]
2026-08-07 19:34 ` [PATCH RFC v3 3/8] scripts/syscall.tbl: Use the common table André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 4/8] arm: Use the common syscall table André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 5/8] s390: " André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 6/8] sparc: " André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 7/8] mips: Remove duplicated syscallnr.sh André Almeida
2026-08-07 19:34 ` [PATCH RFC v3 8/8] mips: Use the common syscall table André Almeida
2026-08-07 21:02 ` Arnd Bergmann
2026-08-10 13:20 ` André Almeida
2026-08-07 20:43 ` [PATCH RFC v3 0/8] syscalls: Add a shared table for all archs Arnd Bergmann
2026-08-10 13:25 ` André Almeida
2026-08-10 14:18 ` Arnd Bergmann
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=3ee5b6f6-8d71-4a01-bd50-3768ddb02b4a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrealmeid@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=tglx@kernel.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
all inboxes | Powered by JetHome®