From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AD929C47077 for ; Tue, 9 Jan 2024 23:18:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ZA9sw6THIgPv2hM5gyc9gCobQHlpRL2L69aqEXodjx4=; b=qYLzEDQuMDa2GM tl9fhGL49W9kbp4MT/LkD7KXWEjOeB26bkwYjGazIakC6Rxhm2k9bth9N2d+Y0HYjlnrRsZLydTKW krZcw4IY9o13M4G0j2FmZox2J1fwFTZ3O6rY4gmfcQVHufFp+AsBVAkhNT01oIbkg57kVqStZ1LoK V+w4RPlYODoWoJ9OzzWgkEJKTxks+7CEKzQekmTeIvegM/W8VKpC5T59LFVdIOJmmlZxnGWOx9xTz hzEAzRc772cNgqD23TL8QFOd+LIUPXC3buDr12AcrH2IshDXxosRMHe7MhTe8Dp1sUeEwBacuNI1E Xy8i/9woygJDJ+0yoUcg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rNLMA-009pHf-2t; Tue, 09 Jan 2024 23:18:02 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rNLM7-009pGd-0T; Tue, 09 Jan 2024 23:18:01 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id B178BB81B6E; Tue, 9 Jan 2024 23:17:56 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2313DC433C7; Tue, 9 Jan 2024 23:17:51 +0000 (UTC) Message-ID: <461a6556-8f24-48f5-811a-498cb44f2d64@linux-m68k.org> Date: Wed, 10 Jan 2024 09:17:48 +1000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Call for nommu LTP maintainer [was: Re: [PATCH 00/36] Remove UCLINUX from LTP] Content-Language: en-US To: Rob Landley , Petr Vorel Cc: Cyril Hrubis , Geert Uytterhoeven , ltp@lists.linux.it, Li Wang , Andrea Cervesato , Jonathan Corbet , Randy Dunlap , John Paul Adrian Glaubitz , Christophe Lyon , linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org, Linux ARM , linux-riscv , Linux-sh list , automated-testing@lists.yoctoproject.org, buildroot@buildroot.org, Niklas Cassel References: <20240103015240.1065284-1-pvorel@suse.cz> <20240103114957.GD1073466@pevik> <5a1f1ff3-8a61-67cf-59a9-ce498738d912@landley.net> <20240105131135.GA1484621@pevik> <90c1ddc1-c608-30fc-d5aa-fdf63c90d055@landley.net> <20240108090338.GA1552643@pevik> From: Greg Ungerer In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240109_151759_548948_21BC36E6 X-CRM114-Status: GOOD ( 29.80 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 10/1/24 06:24, Rob Landley wrote: > On 1/8/24 03:03, Petr Vorel wrote: >> Hi Rob, all, >> >> [ Added Niklas Cassel, who is maintainer of qemu_riscv64_nommu_virt_defconfig in >> buildroot ] > > Hi Niklas! > >>> Buildroot also apparently has an LTP package selectable in menuconfig: >> >>> https://github.com/buildroot/buildroot/tree/master/package/ltp-testsuite >> >>> But I haven't tried it... >> >> I'm the maintainer of the LTP package in buildroot in my private time. >> BTW I spent quite a lot of time fixing LTP (and some other system packages, >> e.g. nfs-utils) compilation on some old legacy architectures reported via >> http://autobuild.buildroot.net/ I've never used in the reality. >> But I certainly don't have time to drive nommu support in my private time. >> I don't even have an interest, I don't use any nommu device. > > I do, but I've never done much with LTP, and I have my hands full with toybox > and mkroot already. > >> Therefore nobody who is not involved in nommu will not find a time to support it >> in LTP (support does not mean just to add the functionality to the new C API, >> but run tests on nommu and fix failing bugs). I suppose nobody is paid to work >> on nommu platforms, it would have to be a hobby project, right? > > A bunch of people are paid to work on nommu platforms, and I've worked with them > a bunch, but none of them talk to linux-kernel. They find the culture toxic, > insular, and categorically dismissive of their interests. I have been involved in the kernel nommu space for 20 years, and sure, there is some of that. But mostly spending some time and effort to get involved pays off. I have seen potential contributors show up with some arrogant attitudes too, so it cuts both ways here. The m68k community I have been part of has been nothing but welcoming. The mm people have tried hard to keep nommu support up-to-date where almost none of them actually have a vested interest in doing so. What I have seen is that many companies working in this space just don't want to spend the time and effort to go mainline. That is a business decision they make, and that is fine. Heck my work in actual mainline has never really been paid for by any company and I have sunk a _lot_ of time into it. (Full disclosure I did get paid to work on early porting and support - just not geting it into mainline and maintain it there). > For example, cortex-m is a large nommu platform on which vendors support Linux > BSPs, but notice how page 8 of > https://www.microsemi.com/document-portal/doc_view/132181-linux-cortex-m-users-manual > points at a cross compiler toolchain from _2010_ and page 4 says they're booting > a 2.6.33 kernel? Any company/person who follows the route of not working with the linux kernel community to get their work included is going to inevitably get stuck on older versions of everything. > I'm a bit weird in that I try to get CURRENT stuff to work on nommu, and a lot > of people have been happy to consume my work, but getting any of them to post > directly to linux-kernel is like pulling teeth. I regularly test nommu configurations (as in every kernel rc and release) on m68k and at least every release on other architectures like arm(*) and recently on riscv as well. (*) somewhat annoyingly needing a minor patch to run the versatile qemu platform I like to test with. But hey, that is on me :-) Regards Greg >> But as I said, if anybody from nommu decides to maintain it in LTP, I'll try to >> support him in my free time (review patches, give advices). And if nobody >> stands, this patchset which removes the support in the old API will be merged >> after next LTP release (in the end of January). > > What does the API migration do? Is there a page on it ala OABI vs EABI in arm or > something? > > Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel