[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220402072138.GI7074@brightrain.aerifal.cx>
Date: Sat, 2 Apr 2022 03:21:38 -0400
From: Rich Felker <dalias@...c.org>
To: 王洪亮 <wanghongliang@...ngson.cn>
Cc: musl@...ts.openwall.com
Subject: Re: Re: add loongarch64 port
On Sat, Apr 02, 2022 at 02:19:44PM +0800, 王洪亮 wrote:
> Hi, Arnd
>
> I found it has not been removed from system call list in kernel yet.
> I wonder if I could keep consistent with the current status of the kernel
> for the time being,and modify as the kernel changes.
As I understand it, no -- musl targets the permanent kernel syscall
API/ABI for the arch. So if the legacy stat syscall is not going to be
part of the interface that's approved upstream in the kernel for this
arch, musl can't be using it.
Am I correct in understanding that the syscall & struct stat that are
"there now" are part of a proposed port that's not yet upstream, and
that upstream maintainers are asking for them to be removed as part of
accepting the port?
> 在 2022/4/1 下午3:48, Arnd Bergmann 写道:
> >On Fri, Apr 1, 2022 at 9:40 AM 王洪亮 <wanghongliang@...ngson.cn> wrote:
> >>在 2022/3/31 下午4:14, Arnd Bergmann 写道:
> >>
> >>In kernel port, loongarch64 use the generic struct stat.
> >>
> >>loongarch64 define struct stat and kstat in musl is consistent with
> >>
> >>generic stat in kernel.
> >My point was that I asked for these to be removed in
> >
> >https://lore.kernel.org/lkml/CAK8P3a2kroHVN3fTabuFVMz08SXytz-SC8X11BxxszsUCksJ4g@mail.gmail.com/
> >
> >With __NR_newfstatat and __NR_fstat gone from the system
> >call list, there is no 'struct stat' that is exposed by the kernel.
> >
> > Arnd
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
