|
Message-ID: <d3db892f-0b91-9ee4-fbb4-3e66125f65c6@loongson.cn> Date: Wed, 6 Apr 2022 10:08:24 +0800 From: 王洪亮 <wanghongliang@...ngson.cn> To: musl@...ts.openwall.com Subject: Re: Re: add loongarch64 port 在 2022/4/2 下午3:59, 王洪亮 写道: > > 在 2022/4/1 上午2:47, Rich Felker 写道: >> On Thu, Mar 31, 2022 at 02:20:51PM +0800, 王洪亮 wrote: >>> 在 2022/3/29 下午4:26, Arnd Bergmann 写道: >>>> On Tue, Mar 29, 2022 at 10:12 AM 王洪亮 <wanghongliang@...ngson.cn> >>>> wrote: >>>>> Hi, >>>>> >>>>> we have published 0001-add-loongarch64-port-v2.patch in >>>>> >>>>> https://github.com/loongson/musl/tree/loongarch-v1.0. >>>>> >>>>> The patch v2 fixed the issues pointed out in v1. >>>>> >>>>> have any other issues to modify? >>>> I see you still refer to the system calls that I asked to be >>>> removed from >>>> the kernel: clone() and the old stat() family (pre-statx). Please use >>>> only the system calls that are actually supported in mainline kernels, >>>> otherwise it does not work. >>> Hi, Arnd >>> >>> I understand the new system call is clone3() ? >>> >>> I found musl does not support the clone3() call now, I can implement >>> the >>> >>> clone3() in LoongArch for future called. >> The point isn't that there should be a clone3() function (there >> shouldn't) but that __clone has to be implemented by making the >> __NR_clone3 syscall not the (nonexistant) __NR_clone syscall. >> Rich > > > Hi, Rich > > > I understand the meaning is that keep the architecture-independent code > and the __clone input parameter unchanged,within the __clone, convert > input parameter to clone3 parameter, and then __NR_clone3 syscall. > > will that confusion between clone and clone3? > > > Hongliang Wang Hi, Rich within __clone() implement __NR_clone3 syscall, will that confusion between clone and clone3? Hongliang Wang
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.