On 6/19/26 11:43, Florian Weimer wrote:
- Fabian Arrotin:
On 6/19/26 08:58, Florian Weimer via devel wrote:
- Amy Marrich via devel:
At the June CentOS Board meeting, we were asked about pain points with hardware in the community to see what the Community Linux Engineering team might be able to assist with. The board came up with a HSM for secureboot and RISC-V hardware, but we want to know - what does the community as a whole think is a hardware pain point we can work on resolving?
Maybe this: Move the AArch64 builders to at least Neoverse-V1, preferably a later generation? It will give us some flexibility in future architecture baseline choices. Similarly, we really need the ppc64le builders to move to POWER10 (but I think that's already tracked as a task).
The cbs koji aarch64 builders are m6g.4xlarge and so already on Neoverse-N1 and for ppc64le these are also Power10 ..
It seems m6g.4xlarge is Graviton2, which uses Neoverse-N1 cores. That's one generation before Neoverse-V1.
(AWS does not commit to specific CPU feature sets for their instance types, so reliable information is kind of hard to come by.)
*ack* and that I can easily change so let me see which instance type we can use that would have Neoverse-V1 and then plan this for a sprint to come (and announce when done but that's trivial)
but I guess you meant for Stream Infra ?
Yes, that as well. Consistency benefits everyone.
Thanks, Florian
Worth knowing that for Stream infra there is actually no planned hardware replacement for aarch64, still on : Model name: Neoverse-N1 BIOS Model name: Ampere(R) Altra(R) Max Processor