From owner-freebsd-current@freebsd.org Fri Apr 9 13:40:42 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6E8A45B8F2F for ; Fri, 9 Apr 2021 13:40:42 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f47.google.com (mail-ot1-f47.google.com [209.85.210.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FGzm941Zrz4kF1; Fri, 9 Apr 2021 13:40:41 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f47.google.com with SMTP id y19-20020a0568301d93b02901b9f88a238eso5678061oti.11; Fri, 09 Apr 2021 06:40:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FGAGhiEVfu1Y8tdWihEfWOV+fVzc+ZPuVloBII+YRLw=; b=aGs8J7C3drYhBVopLbGuYFqhEwgRyripMEGjlPCvV6g2uoFfLq3iSczKgyKddpF+g6 dsTgzXCZf24/9hYU50jsnu0CIJdoqgCZ+7hUBgCWiv4QEInZ2EV1NCiP8SiPTxlInMON Nvil9PmzBIoXdN/eCK5sHqmlFH7r2F3oscYLoTjtLQF/g7aabWbJLopPrQCuBJqiCofR h4utpPMKZk6nlZR+P91C03cXxhZRZRkYxoXwFVDy2JdOG4hBL6njd8IBkHoEqEcQx0HU Y05fIFg4QT2dSlZyDUaKL5Szr4VfjDAbislRCufvnPqRF+JLdXUiCrN4F9X5bCwKCH0Y 0ssQ== X-Gm-Message-State: AOAM53329aPo/uJhsUDKKrIV64hrW6vShYpMpMRTCYTyAhqSLXYidHxo BF++rtlRAlop15yGIBVpDFKl0IKPXgu15JgdxRZFwig1 X-Google-Smtp-Source: ABdhPJzieiL96Xs8Gmfgtm60jR+0qMkDLlXNzyrHyo+YoBqWl+5JQGIGsiPUzOnqGZNyxoB6CBEioADkKvEMSEBdpPA= X-Received: by 2002:a05:6830:1af6:: with SMTP id c22mr11780789otd.291.1617975640024; Fri, 09 Apr 2021 06:40:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Fri, 9 Apr 2021 07:40:28 -0600 Message-ID: Subject: Re: FreeBSD/arm64 becoming Tier 1 in FreeBSD 13 To: Ed Maste Cc: FreeBSD Current X-Rspamd-Queue-Id: 4FGzm941Zrz4kF1 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.47 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-1.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.47:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[freebsd.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.210.47:from]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[209.85.210.47:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.47:from]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2021 13:40:42 -0000 On Fri, Apr 9, 2021 at 7:23 AM Ed Maste wrote: > Summary > > FreeBSD will promote arm64 to a Tier 1 architecture in FreeBSD 13. > This means we will provide release images, binary packages, and > security and errata updates. While we anticipate there will be minor > issues with this first release, we believe the port is mature enough > that they can be resolved during the life of FreeBSD 13. > > Details > > Development efforts on FreeBSD/arm64 (also known as AArch64) started > in 2014, with generous financial and technical support from Arm, > Cavium and the FreeBSD Foundation. FreeBSD 11.0 arrived in October > 2016 as the first release with support for the architecture. > Improvements to the kernel, tool chain, userland, and ports and > package infrastructure have been ongoing since that time, with > improvements arriving in each minor and major release. > > The FreeBSD base system is ready for the promotion of arm64 to Tier 1, > and the Release Engineering, Security, and Ports teams are prepared to > support the Tier 1 requirements for arm64. Security updates via > freebsd-update now include arm64 support (starting with the FreeBSD > 13.0 release candidates). > > Required ports infrastructure is in place for arm64 and most ports > build successfully. The project now has several Ampere eMAG systems > acting as package build servers. These machines were obtained through > a combination of FreeBSD Foundation purchases and generous donations > from Ampere. > > To support port maintainers who do not have access to arm64 hardware > we will be improving ports CI and testing resources (and this effort > will benefit all architectures). We will also be suggesting one or > more low-cost reference platforms for FreeBSD/arm64. > > The guarantees included in Tier 1 status are described in > > https://docs.freebsd.org/en_US.ISO8859-1/articles/committers-guide/archs.= html > > In particular, for Tier 1 architectures the project provides release > images, binary package sets, and binary and source updates for > Security Advisories and Errata Notices. > > The AArch64 ecosystem=E2=80=99s maturity ensures follow on generations of > hardware. The diversity of offerings, as well as the multiple > generations of hardware shows that the FreeBSD project will benefit > from adding support for this platform. The growth trajectory suggests > this will be a significant portion of the market in the coming years, > and FreeBSD will benefit from tapping into this market with this Tier > 1 platform. > > (on behalf of core) > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > Wow, great news! I look forward to seeing your reference platform recommendations. But the next obvious question that comes to mind is: how to do hosted CI testing for FreeBSD/arm64? Cirrus-CI and sr.ht work well but only for amd64. Are there any options for arm64 at all? I think it should be possible to hook up Cirrus's management to one of Amazon's arm64 instances, but somebody would have to go to the trouble of creating a custom ami image, and every user would need to create an EC2 account. Are there any better options? -Alan