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=-5.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8735 invoked from network); 1 Jun 2022 08:10:32 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 1 Jun 2022 08:10:32 -0000 Received: (qmail 32331 invoked by uid 550); 1 Jun 2022 08:10:24 -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 14334 invoked from network); 1 Jun 2022 01:14:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xen0n.name; s=mail; t=1654046039; bh=pMq9NS9OSPMIUB60xzKZhXnr5K83nxwQ8BT9E2zyna8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=IUcZH4S0FgPYhAx2CZ5cPrcna6qZkVxpbP32f4XEImxLpPADWip7X9LJ8dDjXwi9Y gkPH7D3zlvQuVPlKaicnTInLT3w4VG2NHPEtkQFFKfxq5U+JP0FEx4/5V+icuOjiWM ekOBReg5J/qWSZPuVDlqu9VGeGrroQXf3lf9VR+M= Message-ID: Date: Wed, 1 Jun 2022 09:13:58 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Thunderbird/103.0a1 Content-Language: en-US To: Arnd Bergmann , Huacai Chen Cc: musl@lists.openwall.com, WANG Xuerui , Linus Torvalds , linux-arch , GNU C Library , Yoshinori Sato , Peter Zijlstra , Marc Zyngier , Masahiro Yamada , Linux Kernel Mailing List , Jiaxun Yang , ACPI Devel Maling List , Jianmin Lv , linux-pci , Ard Biesheuvel , Huacai Chen References: <358025d1-28e6-708b-d23d-3f22ae12a800@xen0n.name> From: WANG Xuerui In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [musl] Re: [GIT PULL] asm-generic changes for 5.19 On 6/1/22 04:07, Arnd Bergmann wrote: > On Tue, May 31, 2022 at 6:01 PM Huacai Chen wrote: >> On Tue, May 31, 2022 at 7:15 PM Arnd Bergmann wrote: >>> On Tue, May 31, 2022 at 10:17 AM Huacai Chen wrote: >> https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/log/?h=loongarch-next >> has been updated. Now this branch droped irqchip drivers and pci >> drivers. But the existing irqchip drivers need some small adjustment >> to avoid build errors [1], and I hope Marc can give an Acked-by. > Ok, glad you got that working. > > What about the ACPI changes? I see that these are needed to get a clean build, > and as I understood it, they are supposed to get merged through the > acpica tree. I think the acpica bits could be dropped with some effort too; the main dependency on the various ACPI 6.5 tables are the SMP bits, which relies on the new MADT CPUINTC tables. While the others also provide information, they're not as fundamental as this, and even this CPUINTC piece can be taken out given we can't run this branch on any real LoongArch hardware after all (due to the irqchip changes being backed out), I think we can just leave the remaining bits dummy-initialized with some simple comment. We can review once the new branch with only arch/loongarch changes is out. >> This branch can be built with defconfig and allmodconfig (except >> drivers/platform/surface/aggregator/controller.c, because it requires >> 8bit/16bit cmpxchg, which I was told to remove their support). > Right, that is ok to keep in there, we should fix that by adding a Kconfig > dependency for the driver. It looks like it has a CONFIG_ACPI dependency, > so it is currently limited to x86/arm64/ia64, which all have the short > cmpxchg(), > but in reality this driver can only work on x86 and arm64. In case this isn't obvious to any non-native English speaker: the driver is written for the Microsoft Surface, which only has x86 and arm64 variants to this date and the list is probably not going to expand in the foreseeable future, so the word "work" here takes a quite literal sense. ;-) I agree a tiny fix for that driver could be added later that limits the driver to X86 || ARM64. As a popular product line, adding support for yet another architecture would be a news visible enough for the crowd that they'll come and tweak the Kconfig themselves.