From: "Arnd Bergmann" <arnd@arndb•de>
To: "Jiri Olsa" <olsajiri@gmail•com>
Cc: "Stephen Rothwell" <sfr@canb•auug.org.au>,
"Christian Brauner" <brauner@kernel•org>,
"Christian Göttsche" <cgzones@googlemail•com>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the asm-generic tree
Date: Tue, 09 Jul 2024 14:20:26 +0200 [thread overview]
Message-ID: <c25a32c6-8ed0-4ef9-a13e-cb16a89edb73@app.fastmail.com> (raw)
In-Reply-To: <Zo0kzIR_ZueaEjTa@krava>
On Tue, Jul 9, 2024, at 13:53, Jiri Olsa wrote:
> On Tue, Jul 09, 2024 at 01:44:34PM +0200, Arnd Bergmann wrote:
>
>> Though I'm still not sure what uretprobe is only added
>> to half the architectures at the moment. There is a chance
>> we need a different conditional for it than '64'.
>
> uretprobe is defined only for x86_64, not sure what that means
> for scripts/syscall.tbl though
I meant you hooked it up unconditionally for all architectures
using the old method, i.e. arc, arm64, csky, hexagon, loongarch64,
nios2, openrisc, riscv32, riscv64, and xtensa in addition
to x86-64, but not for the other ABIs: alpha, arm32, m68k,
microblaze, mips-o32, mips-n32, mips64, nios2, parisc32, parisc64,
powerpc32, powerpc64, powerpc-spu, s390-31, s390-64, sh,
sparc32, sparc64, x86-32 and x86-x32.
If that is not the list you had intended, do you have a list
of which architectures actually have the required hardware
to hook it up? It would be good to do this correctly from
the start so we don't rely on architecture maintainers assigning
the numbers individually.
ARnd
next prev parent reply other threads:[~2024-07-09 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 0:57 linux-next: manual merge of the vfs-brauner tree with the asm-generic tree Stephen Rothwell
2024-07-09 10:08 ` Stephen Rothwell
2024-07-09 11:44 ` Arnd Bergmann
2024-07-09 11:53 ` Jiri Olsa
2024-07-09 12:20 ` Arnd Bergmann [this message]
2024-07-09 12:42 ` Jiri Olsa
2024-07-09 12:58 ` Arnd Bergmann
2024-07-09 13:17 ` Jiri Olsa
2024-07-09 14:26 ` Arnd Bergmann
2024-07-10 2:22 ` Stephen Rothwell
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=c25a32c6-8ed0-4ef9-a13e-cb16a89edb73@app.fastmail.com \
--to=arnd@arndb$(echo .)de \
--cc=brauner@kernel$(echo .)org \
--cc=cgzones@googlemail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olsajiri@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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