From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web10.53371.1674671267400600665 for ; Wed, 25 Jan 2023 10:27:47 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=b0jHkA1z; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: osteffen@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674671266; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=pUCuKqmDbc/RNFp4939ybLEleTr0BLPliPiYIjzyhu4=; b=b0jHkA1zV40OhHzp+BeOiRyhPzisGxw0veerCYEJuCbb5YxIU3ObSoOTVlqYE2UKzS4vBl /1koVbPEz8X7VNnJOTTBLLArobQ5IVpofLhGjBExM0Zf6D0/n8aH//hhCJkt/GKXiXe3MC 8HlZUvzzT3oy6g7Wmu1S/Ed6VxZoPDM= Received: from mail-lf1-f70.google.com (mail-lf1-f70.google.com [209.85.167.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-574-Wx4-6PmRM36KMD-E9W1jGA-1; Wed, 25 Jan 2023 13:27:45 -0500 X-MC-Unique: Wx4-6PmRM36KMD-E9W1jGA-1 Received: by mail-lf1-f70.google.com with SMTP id y26-20020a0565123f1a00b004b4b8aabd0cso8464422lfa.16 for ; Wed, 25 Jan 2023 10:27:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pUCuKqmDbc/RNFp4939ybLEleTr0BLPliPiYIjzyhu4=; b=6GGXGk/SbG+PmaGFpMY2QI+fkmjiAALxIsSOOZPK5GzHyoo3AWY9jxEz/GolNfHaTQ /vq65YoSM0gh9U+7AMTlvPGFVaANgsguFS2yRltC48w6I1KtsMGRiqQk0yyayG0qOhiy PGmfjZ17VKkBTSQmMZ5VS9LAm4sKTTjfzLbq8B4anLpPub/tSUp7zu50yNlr5hxmRnA9 UgPUF/RZ2ajcCkf29Rsm0klcm8RTyIZmI/Ya3pnY4qpWAuj5bfDYZKKyDFb3rwl24zVc jV1DVhChKSN6c18B+legNGeHnvDAAdyr9bqWaMGzYn440rR+BhyFV4UsqpV4WrwC/H4d Tf2A== X-Gm-Message-State: AFqh2krwTq8qLlVV1otfKTV3nxuKCTobv/LQEbk6FHC5av7Cz7q0GjLl aviCphASYlBFFUAR4V8Mp26yK8GIUZfJGt6PH/OznViTZhMUKh4JTqE2oLklumr0TJF0NEEuZK6 fbuoLwNlQkYD5pJS0V/rPTJIsQ3reSw== X-Received: by 2002:a05:6512:746:b0:4d2:e530:d54e with SMTP id c6-20020a056512074600b004d2e530d54emr1737172lfs.656.1674671263717; Wed, 25 Jan 2023 10:27:43 -0800 (PST) X-Google-Smtp-Source: AMrXdXsEvdRtkAPIKvXe47BTp1TVNApYL/oV22BwpGLx3MtXpkL0XDyAcw8LP9MHa7PemAWSxRVKYQx6KIhc1xQuPcs= X-Received: by 2002:a05:6512:746:b0:4d2:e530:d54e with SMTP id c6-20020a056512074600b004d2e530d54emr1737165lfs.656.1674671263469; Wed, 25 Jan 2023 10:27:43 -0800 (PST) MIME-Version: 1.0 References: <20230125165556.tvp7cgjsj2kie7b6@sirius.home.kraxel.org> In-Reply-To: <20230125165556.tvp7cgjsj2kie7b6@sirius.home.kraxel.org> From: "Oliver Steffen" Date: Wed, 25 Jan 2023 19:27:32 +0100 Message-ID: Subject: Re: arm64 support for stuart To: Gerd Hoffmann Cc: Ard Biesheuvel , Michael Kubacki , Sean Brogan , Michael Kinney , edk2-devel-groups-io , Jiewen Yao X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="000000000000c66c8a05f31ac910" --000000000000c66c8a05f31ac910 Content-Type: text/plain; charset="UTF-8" On Wed, Jan 25, 2023 at 5:56 PM Gerd Hoffmann wrote: > Hi, > > > Given that nasm is x86 specific, we should be able to work around this > > by moving the nasm_ext_dep.yaml file into the right place. > > Overall stuart feels kind of alien to linux. It just goes download > stuff from the internet, even in case the tools are already available > locally. Oliver fixed some (but not all) of these when moving CI over > to using containers. IIRC at least the cross compilers are just the > standard fedora cross compiler packages now. > > While being at it: edk2-pytool-library fails to build with network > access turned off[1] because it tries to download vswhere.exe from the > internet. Even when building on linux. > > > Then, if/when mu_nasm for arm64 becomes available, we will also be > > able to build OVMF from arm64 (although I am probably the only person > > in the world who does that regularly.) > > Fedora build system does that too. We have a patch to make x86 cross > builds work like arm cross builds, by just setting GCC5_${ARCH}_PREFIX > environment variable: > > https://github.com/kraxel/edk2/commit/6b2ca6f01bb76a3b9632e902b4bf0ef9e912ce40 > > Guess I should submit that one for upstream inclusion ;) > > > iasl is a different matter, as we need it to build for arm64 as well. > > iasl is already available in the arm64 distros, so as I see it, there > > are 3 options here: > > - build iasl for Linux/arm64 and add it to the nuget repo > > - allow a fallback to system-wide iasl (how?) > > Just use the system-wide tools is the best option IMHO. The packages > are available in Fedora (other distros should be have them too), on both > x86_64 and aarch64, we only need to add them to the CI container image. > So why bother adding nuget builds? > > That is also less fragile than downloading them on each CI run and have > checks fail now and then due to network problems. > > Is it possible to run github actions (used to build containers) and > azure pipelines on aarch64 systems? So we could move ArmVirt CI from > x86 cross builds to native arm builds? Not natively, AFAIK, at least not without self-hosting a runner or using 3rd-party services. Most suggestions I came across suggest running in Qemu (tcg)... > > take care, > Gerd > > [1] Offline builds are standard for linux distro builds to make sure > all sources needed are to produce the binary package are actually > included in the source package. > > --000000000000c66c8a05f31ac910 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Jan 25, 2023 at 5:56 PM Gerd Hoffmann <<= a href=3D"mailto:kraxel@redhat.com">kraxel@redhat.com> wrote:
=C2=A0 Hi,

> Given that nasm is x86 specific, we should be able to work around this=
> by moving the nasm_ext_dep.yaml file into the right place.

Overall stuart feels kind of alien to linux.=C2=A0 It just goes download stuff from the internet, even in case the tools are already available
locally.=C2=A0 Oliver fixed some (but not all) of these when moving CI over=
to using containers.=C2=A0 IIRC at least the cross compilers are just the standard fedora cross compiler packages now.

While being at it:=C2=A0 edk2-pytool-library fails to build with network access turned off[1] because it tries to download vswhere.exe from the
internet.=C2=A0 Even when building on linux.

> Then, if/when mu_nasm for arm64 becomes available, we will also be
> able to build OVMF from arm64 (although I am probably the only person<= br> > in the world who does that regularly.)

Fedora build system does that too.=C2=A0 We have a patch to make x86 cross<= br> builds work like arm cross builds, by just setting GCC5_${ARCH}_PREFIX
environment variable:
=C2=A0 https://github.= com/kraxel/edk2/commit/6b2ca6f01bb76a3b9632e902b4bf0ef9e912ce40

Guess I should submit that one for upstream inclusion ;)

> iasl is a different matter, as we need it to build for arm64 as well.<= br> > iasl is already available in the arm64 distros, so as I see it, there<= br> > are 3 options here:
> - build iasl for Linux/arm64 and add it to the nuget repo
> - allow a fallback to system-wide iasl (how?)

Just use the system-wide tools is the best option IMHO.=C2=A0 The packages<= br> are available in Fedora (other distros should be have them too), on both x86_64 and aarch64, we only need to add them to the CI container image.
So why bother adding nuget builds?

That is also less fragile than downloading them on each CI run and have
checks fail now and then due to network problems.

Is it possible to run github actions (used to build containers) and
azure pipelines on aarch64 systems?=C2=A0 So we could move ArmVirt CI from<= br> x86 cross builds to native arm builds?
=C2=A0
Not natively, AFAIK, at least not= without self-hosting a runner or using 3rd-party
services.
= Most suggestions I = came across suggest running in Qemu (tcg)...
=C2=A0

take care,
=C2=A0 Gerd

[1] Offline builds are standard for linux distro builds to make sure
=C2=A0 =C2=A0 all sources needed are to produce the binary package are actu= ally
=C2=A0 =C2=A0 included in the source package.

--000000000000c66c8a05f31ac910--