From nobody Tue Nov 18 17:18:19 2025 X-Original-To: arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4d9rt82mMYz6HSpw for ; Tue, 18 Nov 2025 17:18:24 +0000 (UTC) (envelope-from tpearson@raptorengineering.com) Received: from raptorengineering.com (mail.raptorengineering.com [23.155.224.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4d9rt75r8Bz3D3W for ; Tue, 18 Nov 2025 17:18:23 +0000 (UTC) (envelope-from tpearson@raptorengineering.com) Authentication-Results: mx1.freebsd.org; none Received: from localhost (localhost [127.0.0.1]) by mail.rptsys.com (Postfix) with ESMTP id 943DA7790E26; Tue, 18 Nov 2025 11:18:22 -0600 (CST) Received: from mail.rptsys.com ([127.0.0.1]) by localhost (vali.starlink.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Z_dMxX_ywL2U; Tue, 18 Nov 2025 11:18:22 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mail.rptsys.com (Postfix) with ESMTP id DB98E7790ECD; Tue, 18 Nov 2025 11:18:21 -0600 (CST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.rptsys.com DB98E7790ECD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raptorengineering.com; s=B8E824E6-0BE2-11E6-931D-288C65937AAD; t=1763486301; bh=aHQ9hyNJCghFYdNv0PvsdQjAk85CAteQE0bZ9qb5mas=; h=Date:From:To:Message-ID:MIME-Version; b=TalBTe87Kb1tyQg7CiRey1lzGjma7Af9ZGNVliovAYsjfXJXaMi5Aaymih/j6rnWL mBoCcnxYT54TTw6S7s+tCEeXP1PS98rKFVdySbHMA9O+Mf5NOMM63qcomwkOiq2It7 bDA9DA42v+e5VBZoH0E2xStucRyvMiW6m78vrCD8= X-Virus-Scanned: amavisd-new at rptsys.com Received: from mail.rptsys.com ([127.0.0.1]) by localhost (vali.starlink.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id edH3DxGZfdx3; Tue, 18 Nov 2025 11:18:21 -0600 (CST) Received: from vali.starlink.edu (localhost [127.0.0.1]) by mail.rptsys.com (Postfix) with ESMTP id B0FF57790E26; Tue, 18 Nov 2025 11:18:21 -0600 (CST) Date: Tue, 18 Nov 2025 11:18:19 -0600 (CST) From: Timothy Pearson To: Konstantin Belousov Cc: Warner Losh , "freebsd-arch@freebsd.org" Message-ID: <103937333.116931.1763486299091.JavaMail.zimbra@raptorengineeringinc.com> In-Reply-To: References: <1795409779.114152.1763457185418.JavaMail.zimbra@raptorengineeringinc.com> <875004641.116392.1763457737172.JavaMail.zimbra@raptorengineeringinc.com> <1827088521.116443.1763460735444.JavaMail.zimbra@raptorengineeringinc.com> Subject: Re: What's the plan for powerpc64 in FreeBSD 16 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.5.0_GA_3042 (ZimbraWebClient - GC141 (Linux)/8.5.0_GA_3042) Thread-Topic: What's the plan for powerpc64 in FreeBSD 16 Thread-Index: 228seaRWBqA7VTwskDhNfLTurFLkyg== X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:46246, ipnet:23.155.224.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4d9rt75r8Bz3D3W ----- Original Message ----- > From: "Konstantin Belousov" > To: "Timothy Pearson" > Cc: "Warner Losh" , "freebsd-arch@freebsd.org" > Sent: Tuesday, November 18, 2025 5:11:39 AM > Subject: Re: What's the plan for powerpc64 in FreeBSD 16 > On Tue, Nov 18, 2025 at 04:12:15AM -0600, Timothy Pearson wrote: >> >> >> ----- Original Message ----- >> > From: "Konstantin Belousov" >> > To: "Timothy Pearson" >> > Cc: "Warner Losh" , "freebsd-arch@freebsd.org" >> > >> > Sent: Tuesday, November 18, 2025 4:09:41 AM >> > Subject: Re: What's the plan for powerpc64 in FreeBSD 16 >> >> > Can we please, as the part of the commitment for the ppc support, have >> > a patch submitted for the rtld wart fix? >> > I mean, we should have properly architectured hook for ppc64 to do the >> > hack in libexec/rtld-elf/rtld.c under the #ifdef powerpc, for auxv >> > renumbering compat. >> >> I don't see why not. This is exactly the reason we have FTE resources assigned >> to maintain the software ecosystem for ppc64 -- if there are any other such >> issues just let me know and I'll make sure they get fixed. > > Great. > In fact, I went ahead and drafted the change I want, in > https://reviews.freebsd.org/D53801 > > I am not sure if this is needed for both ppc and ppc64/ppc64le. > Also I did not handled other arches until ppc part is finalized. > > Could you please get somebody answer the question above, and then > have the patch tested, please? Great, thank you for putting that together! This should be required for all ppc* including 32-bit per my understanding. As a historical note / aside, 32-bit support is not of any importance to the general modern POWER ecosystem at this point; I'm on the architectural committee handling the ISA specification, and in general we have no desire to attempt to add 32-bit support to the current POWER standards. I personally wouldn't be opposed to seeing 32-bit support disappear at this point; it was never properly standardized and I have no idea what kind of hardware would actually execute 32-bit FreeBSD kernels at this point. I'll get testing results back later today and update the diff log. One other question -- is there a way Raptor (or even just myself) can get approval rights for changes that touch the ppc* code? One of the reasons we haven't been pushing as much code upstream as we'd like is that we've had a lot of stalls in the review and merge process due to what I assume is lack of reviewer availability / hardware availability, and I want to see if we can help make that process faster. We have a datacenter full of POWER boxes and would be happy to provide remote access (including bare metal) free of charge to anyone that is blocked on hardware availability. Thanks again!