Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 8 May 2021 13:16:34 +0800 (GMT+08:00)
From: 翟小娟 <>
Cc: 陈国祺 <>
Subject: Re: Re: Port the new architecture loongarch64 to musl

Yes, we are still using faccessat on the kernel. After the kernel is updated later, we will eliminate these system calls in the musl source code.
We have already adapted the tool chain, libc, kernel and qemu source code. To ensure quality, we are currently undergoing further testing and verification. We plan to start submitting to the community next month. If necessary, we can provide a physical machine or qemu.

&gt; -----原始邮件-----
&gt; 发件人: "Arnd Bergmann" <>
&gt; 发送时间: 2021-05-08 05:58:15 (星期六)
&gt; 收件人:
&gt; 抄送: "陈国祺" <>
&gt; 主题: Re: [musl] Port the new architecture loongarch64 to musl
&gt; On Fri, May 7, 2021 at 11:01 AM 翟小娟 <> wrote:
&gt; &gt;
&gt; &gt; Hi,
&gt; &gt; I ported a new architecture loongarch64 on the latest branch of musl master. It has been successfully compiled and run the official test libraries libc-testsuit and libc-test of musl.
&gt; &gt; The source code of the prot has been published in  Or check the attachment 0001-port-to-loongarch64.patch, it is the transplanted patch file.
&gt; It's nice to see upstreaming work for loongarch64.
&gt; I'm mainly interested in the kernel side of this, as I review any new
&gt; ports of Linux
&gt; to new architectures.
&gt; Looking at the system call interfaces, I see that you used the generic ABI,
&gt; so there is a good chance that this will not require incompatible changes,
&gt; but a proper review of the kernel port will be necessary to be sure.
&gt; I did notice that the system call list is a bit outdated and does not
&gt; reflect the
&gt; latest kernel, but that should be easy to change. There are a few system calls
&gt; that are technically obsoleted by newer variants now, and we may decide to
&gt; drop them for new architectures in favor of the newer variants, e.g. openat,
&gt; faccessat, and io_getevents.
&gt; The order I would generally recommend for upstreaming is:
&gt; 1. toolchain (either gcc/binutils or clang)
&gt; 2. kernel
&gt; 3. libc
&gt; 4. everything else
&gt; If you do the order differently, there is a risk that ABI changes in one of the
&gt; lower levels require changing the upper levels later on.
&gt;         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.