Secure Boot is still supported in that configuration, but with PK/db/dbx being part of the firmware configuration and updating them requiring a UEFI capsule update.
SME2 is restricted in scope to matrix multiply workloads and isn't really designed for anything else.
The point of streaming SVE is to have a way to pre/post process data on the way in or out of a matrix multiply.
A list that I have around of chips which support various levels of SVE:
For SVE(1) deployment, chips that have it:
- Fujitsu A64fx
- AWS Graviton3
SVE2:
- Snapdragon X2, 8/8 Elite Gen 5 and later
- MediaTek Dimensity 9000 and later
- NVIDIA Tegra Thor and later, NVIDIA "N1" or later (GB10 is an "N1x" SKU)
- Samsung Exynos 2200 or later
- AWS Graviton4, Microsoft Cobalt 100, Google Axion (and newer chips)
- CIX P1
SME(1) instead of SME2:
- Snapdragon X2, 8/8 Elite Gen 5
SME2:
- Apple M4, A18 and later
- Samsung Exynos 2600
- MediaTek Dimensity 9500
Note that the Snapdragon 8/8 Elite Gen 5 and X2 support sve2 but not svebitperm.
There are Intel CPUs which come with bundled RAM. For example Intel Core Ultra 5 238V. It's like SoM: RAM is mounted directly on the CPU package, not even soldered on the motherboard. I'm not sure what particular advantages does that bring over traditional packaging, maybe shorter wires to allow for faster turnarounds between CPU and RAM. But there's zero chance of upgrading or replacing RAM for sure.
In theory, but that is not the case with Lunar Lake, which nowadays does not have a greater bandwidth than the current CPUs with external LPDDR memory.
However, at launch, a year and a half ago, it had a bandwidth about 15% higher than competing CPUs.
For a really "massive increase in bandwidth", it would have needed a wider memory interface, like AMD Ryzen Max, which has a 256-bit memory interface, instead of the 128-bit memory interface of most Intel/AMD laptop CPUs.
Yes, totally. By introduced I didn't mean they were the first in the space but rather they have introduced it to the laptops they're shipping now. But yes, it's been a thing for awhile on other architectures as well.
> While the parent article shows AMD Zen 5 having significantly better results in floating-point SPEC CPU2017, these benchmark results are still misleading, because in properly optimized for AVX-512 applications the difference between Zen 5 and Cortex-X925 would be much greater. I have no idea how SPEC has been compiled by the author of the article, but the floating-point results are not consistent with programs optimized for Zen 5.
The arithmetic intensity of most SPECfp subtests is quite low. You see this wall because it ends up reaching bandwidth limitations long before running out of compute on cores with beefy SIMD.
UEFI without runtime UEFI variable writes is a thing, and that configuration is incompatible with mokutil.
reply