Re: Let's include powerpc64le-linux in the next release
Hello, On Tue, Mar 30, 2021 at 10:24 AM Ludovic Courtès wrote: > Plus, I’m really grateful to OSUOSL for giving > us access to this machine! Yes, it's really nice to have access to those, and in the future, if we want to really support the ppc64le with substitutes, we may ask for a CI-class VM which should have better performance. I've also asked for details of the openstack setup, and the virtual disks provided to the VMs are networked ceph storage which is quite slow, they are investigating the problem. I also asked if they can try to provide hypervisor-local scratch storage (way faster but not durable, and would make the VM non migratable) to the VMs and they may be able to do so in the future. Tchuss -- Vincent Legoll
Re: Let's include powerpc64le-linux in the next release
Hi Tobias, Tobias Geerinckx-Rice skribis: > Ludovic Courtès 写道： >> Like Efraim wrote, the person who makes the release (I’m afraid >> it’ll be >> me) needs to be able to offload to a “trustworthy” machine for that >> platform. > > Define trustworthy? I put quotes because it’s informally defined, at best, and it’s not all or nothing. To me one criterion would be that only known project contributors are admins, physical access to the machine is limited to them and/or a well-identified group of people, and that no build results flow from the outside into this machine. I realize we’re not there yet, but it’s OK: we’re just getting started with this architecture. Plus, I’m really grateful to OSUOSL for giving us access to this machine! Ludo’.
Re: Let's include powerpc64le-linux in the next release, Re: Let's include powerpc64le-linux in the next release
Tobias Geerinckx-Rice writes: > Ludovic Courtès 写道： >> Like Efraim wrote, the person who makes the release (I’m afraid >> it’ll be >> me) needs to be able to offload to a “trustworthy” machine for that >> platform. > > Define trustworthy? The project has access to an 8-core POWER9 VM > from OSUOSL, currently running Debian, to which efraim, lle-bout, > vincele, and me have root access. That would probably work. My understanding is that because we cannot install Guix from an existing release binary, somebody will need to manually build Guix on that machine first, for offloading to work. I can help with this. Ludovic Courtès writes: > If we can do that, we should adjust the ‘release’ target in > ‘Makefile.am’ to do that. > > However, since we won’t be providing substitutes, we should label it as > “technology preview” in the manual (info "(guix) GNU Distribution"). OK! I was planning to add some commits to update the docs, anyway. I can do those two tasks. Additionally, I plan to finally merge wip-ppc64le-for-master to master later today. I'll send a note when that's done. -- Chris signature.asc Description: PGP signature
Re: Let's include powerpc64le-linux in the next release
Ludo', Ludovic Courtès 写道： Like Efraim wrote, the person who makes the release (I’m afraid it’ll be me) needs to be able to offload to a “trustworthy” machine for that platform. Define trustworthy? The project has access to an 8-core POWER9 VM from OSUOSL, currently running Debian, to which efraim, lle-bout, vincele, and me have root access. Kind regards, T G-R signature.asc Description: PGP signature
Re: Let's include powerpc64le-linux in the next release
On Tue, 2021-03-23 at 14:42 +0100, Ludovic Courtès wrote: > Like Efraim wrote, the person who makes the release (I’m afraid it’ll > be > me) needs to be able to offload to a “trustworthy” machine for that > platform. > > If we can do that, we should adjust the ‘release’ target in > ‘Makefile.am’ to do that. > > However, since we won’t be providing substitutes, we should label it > as > “technology preview” in the manual (info "(guix) GNU Distribution"). > > How does that sound? > > Ludo’. Sounds good! Ludo, what is your SSH public key so I can give you access to the powerpc64le-linux machine nckx has gotten from OSUOSL? Thank you! signature.asc Description: This is a digitally signed message part
Re: Let's include powerpc64le-linux in the next release
Hi Chris, Chris Marusich skribis: > How shall we build the binary tarball for the release? Of course, > anybody with a copy of the (source) release tarball can build their own > guix binary by invoking "make guix-binary.powerpc64le-linux.tar.xz" > themselves. However, for convenience, it would be nice to provide a > pre-built binary if possible. Shall I build this myself when the time > comes, or would people prefer to do it a different way? Like Efraim wrote, the person who makes the release (I’m afraid it’ll be me) needs to be able to offload to a “trustworthy” machine for that platform. If we can do that, we should adjust the ‘release’ target in ‘Makefile.am’ to do that. However, since we won’t be providing substitutes, we should label it as “technology preview” in the manual (info "(guix) GNU Distribution"). How does that sound? Ludo’.
Re: Let's include powerpc64le-linux in the next release (was: Re: Release on April 18th?)
On Tue, 2021-03-16 at 09:08 +0200, Efraim Flashner wrote: > On Mon, Mar 15, 2021 at 09:03:04PM -0700, Chris Marusich wrote: > > How shall we build the binary tarball for the release? Of course, > > anybody with a copy of the (source) release tarball can build their > > own > > guix binary by invoking "make guix-binary.powerpc64le-linux.tar.xz" > > themselves. However, for convenience, it would be nice to provide > > a > > pre-built binary if possible. Shall I build this myself when the > > time > > comes, or would people prefer to do it a different way? > > > > When aarch64 support was very new I gave ludo access to my board and > he > offloaded the build to it. > > We have one ppc64le VM from OSUOSL which would qualify as "GNU Guix owned" that nckx, myself, Efraim and Vincent Legoll have access to, so we should definitely use that. We will be working into having that VM added into Cuirass CI as soon as possible after merge into master too. signature.asc Description: This is a digitally signed message part
Re: Let's include powerpc64le-linux in the next release (was: Re: Release on April 18th?)
On Mon, Mar 15, 2021 at 09:03:04PM -0700, Chris Marusich wrote: > > How shall we build the binary tarball for the release? Of course, > anybody with a copy of the (source) release tarball can build their own > guix binary by invoking "make guix-binary.powerpc64le-linux.tar.xz" > themselves. However, for convenience, it would be nice to provide a > pre-built binary if possible. Shall I build this myself when the time > comes, or would people prefer to do it a different way? > When aarch64 support was very new I gave ludo access to my board and he offloaded the build to it. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Let's include powerpc64le-linux in the next release (was: Re: Release on April 18th?)
Hi, I have good news! Chris Marusich writes: > Subject: [PATCH] syscalls: mount: Fix a matching bug. If there are no concerns about this patch, I will commit it to master (with the "mount" typo fixed so it reads "mounts") in the next few days. > Efraim Flashner writes: > >> I'm now running make guix-binary.powerpc64le-linux.tar.xz and so far >> it's made it past the initial building stages, we're on to building the >> grafts now. > > Thank you. This fixed the patch-related problem for me, too. I'm > currently running "make guix-binary.powerpc64le-linux.tar.xz", also, on > my Debian ppc64le machine. We'll see how far it gets - fingers crossed! I'm happy to report that I was able to do all of the following things successfully on the wip-ppc64le-for-master branch after (1) applying the syscalls patch mentioned above, (2) running "make update-guix-package", and (3) locally committing the updated guix package: - On a bare metal Debian ppc64le machine, I ran "make guix-binary.powerpc64le-linux.tar.xz" successfully. - I installed the resulting guix binary in a fresh Debian ppc64le VM successfully. - In the VM, using the newly installed guix binary, I successfully ran "guix pull" to update Guix to the commit I made in (3) above. - In the VM, using the newly pulled guix, I built GNU Hello and verified that it ran successfully. This demonstrates that wip-ppc64le-for-master is working. Therefore, we should merge it to master and officially include powerpc64le-linux support in the next Guix release! Thank you, Efraim, for taking the initiative to adapt some of the commits from wip-ppc64le so they could be applied to master without rebuilding the world on other systems. I've verified that the wip-ppc64le-for-master branch does not rebuild the world. I did this by verifying that the derivations for the "hello" and "gcc-toolchain" packages were the same at the branch point as they are at the tip of the branch (e.g.: ./pre-inst-env guix build -d hello). As I see it, the next tasks for powerpc64le-linux in this release are: - Do a final rebase of wip-ppc64le-for-master, then merge it to master. - When the release happens, make a guix-binary.powerpc64le-linux.tar.xz available wherever binary releases are normally published. - Start building powerpc64le-linux substitutes in the build farm, ideally on POWER9 hardware. How shall we build the binary tarball for the release? Of course, anybody with a copy of the (source) release tarball can build their own guix binary by invoking "make guix-binary.powerpc64le-linux.tar.xz" themselves. However, for convenience, it would be nice to provide a pre-built binary if possible. Shall I build this myself when the time comes, or would people prefer to do it a different way? -- Chris signature.asc Description: PGP signature
