From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8394 invoked from network); 9 May 2021 07:59:08 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 9 May 2021 07:59:08 -0000 Received: (qmail 15626 invoked by uid 550); 9 May 2021 07:57:15 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 15556 invoked from network); 9 May 2021 07:57:14 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1620547021; bh=7Hwzj1LbrKSrw+qSd6YKTlqtV361SS0F09AYIWG1nTs=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=ebR/E5dTTrPofciXBFW+ufaAGocOBR82SZLlHva7SX/elNkDDeDEIiGhUwyIgZ2cY ptqiWSLOYJ5F/YwX1u273xy4Bz9J9WJOSVVlC1o3PLpjWxIc3yi7JYK1C8WZtF4Tiz 5C/RENXJ63ZfF1ZM9fZ2bHNY5r4H7psmSDqXLFkY3xhcieAc/sB+ed+PtqXJSVqYpt TiVaE3AUwZwChAZ17Ilgho5qPrs3RdltUMTCGbHdCHu2wpbmFcANbNcGT1YqE9azk6 6yjoXeDVXocB/q8lXWOiYEGjXqqb+uKPED8kxHGc3lTNLnvy5vEn9LHUOYt9OX+uIm uQyWxJcA/ceZg== X-Gm-Message-State: AOAM531eR7vQ1ivVvc94/RNGz/8NXlBYmOXCpH55rC4uTYEpAsKVufUK /hLVymgwtCY6IIYIZYvyYF/GBIci18JS6BcghpY= X-Google-Smtp-Source: ABdhPJwIqNw7rVteSyu6t4gsggxCmNDK8k+dSw3jHuyryNHAZsBocWIgH1K3+SYeL2debEjAqySJHWMml4JOgFMRd6U= X-Received: by 2002:aca:3389:: with SMTP id z131mr21322563oiz.11.1620547021100; Sun, 09 May 2021 00:57:01 -0700 (PDT) MIME-Version: 1.0 References: <5f6d09a5.c3a.179460eee20.Coremail.zhaixiaojuan@loongson.cn> <4bbba788.12cd.1794a67eb23.Coremail.zhaixiaojuan@loongson.cn> In-Reply-To: <4bbba788.12cd.1794a67eb23.Coremail.zhaixiaojuan@loongson.cn> From: Arnd Bergmann Date: Sun, 9 May 2021 09:56:10 +0200 X-Gmail-Original-Message-ID: Message-ID: To: musl@lists.openwall.com Cc: =?UTF-8?B?6ZmI5Zu956W6?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: Re: [musl] Port the new architecture loongarch64 to musl On Sat, May 8, 2021 at 7:16 AM =E7=BF=9F=E5=B0=8F=E5=A8=9F wrote: > > Yes, we are still using faccessat on the kernel. After the kernel is upda= ted 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. I can clarify what is required for merging the kernel port from my perspect= ive: - In order to review the kernel port on the mailing list, it needs to be based on the latest release, and split up into multiple patches that provide a logical grouping. - For the initial review, no toolchain, hardware or emulator support is nee= ded. - When merging the kernel, any review comments have to be addressed, either by modifying the code, or by concluding that your original version was correct. - Before the kernel is merged, I would expect at the minimum a confirmation from the toolchain maintainers that the compiler can be fully merged into their following release. If you have a patch against gcc-11 and recent binutils, I can create cross-compiler binaries to build kernels and host them along with the release builds at https://mirrors.edge.kernel.org/pub/tools/crosstool/. - Validation is *not* a requirement before sending code for review, and I would consider it a waste of your time, since the review tends to find issues that require invasive changes. I expect that validation is part of your process for shipping software to your users, but the part I care about for mainline support is that the source is maintainable in a way that lets others address problems they find. - qemu support is definitely appreciated, but not a requirement. I'm personally not planning to run your kernels in qemu as part of the review, but others might want to add loongarch qemu to their automated test farms. If you have a working kernel source tree that you need to rebase before sending it for review, I can offer you to take an initial look off-list to point out issues you should address during the rebase. Arnd