Because Sapphire Rapids and Granite Rapids expose the same flags in /proc/cpuinfo (some GR-specific flags are not exposed by the kernel), we opted for a workaround that checks the CPU model number in #299. This solves the issue for Granite Rapids itself, but it also means that any newer CPU will not fall back to the Granite Rapids stack; instead it will use the Sapphire Rapids stack.
We should try to come up with a better solution for this. One possible solution could be to use additional tools like cpuid or cpu_features to find all relevant flags.
Because Sapphire Rapids and Granite Rapids expose the same flags in
/proc/cpuinfo(some GR-specific flags are not exposed by the kernel), we opted for a workaround that checks the CPU model number in #299. This solves the issue for Granite Rapids itself, but it also means that any newer CPU will not fall back to the Granite Rapids stack; instead it will use the Sapphire Rapids stack.We should try to come up with a better solution for this. One possible solution could be to use additional tools like cpuid or cpu_features to find all relevant flags.