From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v4 08/13] LoongArch: Linux Syscall Interface
Date: Wed, 11 May 2022 10:20:46 -0300 [thread overview]
Message-ID: <bfa4a621-32f4-fbc9-9610-00e451be1da9@linaro.org> (raw)
In-Reply-To: <CAK8P3a338fzKQEaWLyvUgQn_rNEsHzKWgq4BLrKvSF8+Ngn1Dw@mail.gmail.com>
On 11/05/2022 04:02, Arnd Bergmann wrote:
> On Mon, May 9, 2022 at 4:26 AM caiyinyu <caiyinyu@loongson.cn> wrote:
>
>> +#define __NR_clone 220
>> +#define __NR_clone3 435
>
>> +#define __NR_fstat 80
>> +#define __NR_newfstatat 79
>
> stat() and newfstatat() are not in the current ABI for the kernel, this needs
> to be updated, and the libc wrapper updated to call statx() instead.
Assuming a minimal kernel version for loongarch higher than 4.11 (where glibc
assumes statx support), these stat definitions does not matter. The
sysdeps/unix/sysv/linux/fstatat64.c (which will be the only use since the
port will be LFS as default) will always call fstatat64_time64_statx without
any fallback.
It is still wrong to place them in the loongarch arch-syscall.h, it means that
either update-syscall-lists.py has an issue or some bogus kernel headers were
used to generate it.
>
> clone() is still an open question, this may have to be implemented on top
> of clone3()
>
> Arnd
next prev parent reply other threads:[~2022-05-11 13:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 2:25 [PATCH v3 00/13] GLIBC LoongArch PATCHES caiyinyu
2022-05-09 2:25 ` [PATCH v4 01/13] LoongArch: Update NEWS and README for the LoongArch port caiyinyu
2022-05-11 17:05 ` Adhemerval Zanella
2022-05-09 2:26 ` [PATCH v4 02/13] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2022-05-09 2:26 ` [PATCH v4 03/13] LoongArch: Add relocations and ELF flags to elf.h and scripts/glibcelf.py caiyinyu
2022-05-09 2:26 ` [PATCH v4 04/13] LoongArch: ABI Implementation caiyinyu
2022-05-09 2:26 ` [PATCH v4 05/13] LoongArch: Thread-Local Storage Support caiyinyu
2022-05-09 2:26 ` [PATCH v4 06/13] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-05-09 2:26 ` [PATCH v4 07/13] LoongArch: Atomic and Locking Routines caiyinyu
2022-05-09 2:26 ` [PATCH v4 08/13] LoongArch: Linux Syscall Interface caiyinyu
2022-05-11 7:02 ` Arnd Bergmann
2022-05-11 13:20 ` Adhemerval Zanella [this message]
2022-05-15 7:53 ` caiyinyu
2022-05-16 18:44 ` Adhemerval Zanella
2022-05-09 2:26 ` [PATCH v4 09/13] LoongArch: Linux ABI caiyinyu
2022-05-11 7:08 ` Arnd Bergmann
2022-05-11 13:27 ` Adhemerval Zanella
2022-05-11 17:32 ` Joseph Myers
2022-05-15 3:32 ` caiyinyu
2022-05-16 18:49 ` Adhemerval Zanella
2022-05-18 3:40 ` caiyinyu
2022-05-18 7:33 ` Arnd Bergmann
2022-05-09 2:26 ` [PATCH v4 10/13] LoongArch: Add ABI Lists caiyinyu
2022-05-10 19:37 ` [PATCH v3 00/13] GLIBC LoongArch PATCHES Florian Weimer
2022-05-10 20:33 ` Joseph Myers
2022-05-11 6:57 ` Arnd Bergmann
2022-05-11 13:17 ` Adhemerval Zanella
2022-05-09 2:29 [PATCH v4 " caiyinyu
2022-05-09 2:30 ` [PATCH v4 08/13] LoongArch: Linux Syscall Interface caiyinyu
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=bfa4a621-32f4-fbc9-9610-00e451be1da9@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).