mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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:58:06 +0200	[thread overview]
Message-ID: <736fde6a-7b2a-4920-af1e-1ad2358db785@app.fastmail.com> (raw)
In-Reply-To: <Zo0wG8e7BwudENQI@krava>

On Tue, Jul 9, 2024, at 14:42, Jiri Olsa wrote:
> On Tue, Jul 09, 2024 at 02:20:26PM +0200, Arnd Bergmann wrote:
>> 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.
>
> hum, so it's hooked in:
>   190fec72df4a uprobe: Wire up uretprobe system call
>
> and the intention is to have it ONLY for x86_64 (as stated above),
> if that's not what happened I need to fix it, please let me know
> what's the problem

If this cannot be used on any other architectures, I would
suggest adding it to the architecture specific list instead,
probably number #335, which is unused on x86-64.

I was under the assumption that this would theoretically be
useful for non-x86 architectures in the future, in which
case you should reserve the same syscall number everywhere
now and rely the stub in kernel/sys_ni.c for those that are
missing the implementation.

     Arnd

  reply	other threads:[~2024-07-09 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  0:57 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
2024-07-09 12:42         ` Jiri Olsa
2024-07-09 12:58           ` Arnd Bergmann [this message]
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=736fde6a-7b2a-4920-af1e-1ad2358db785@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=cgzones@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olsajiri@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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®