AVX-512 wurde dem Kunden aber nicht Garantiert und schon vor dem Release für ADL gestrichen. Die Mainboard Hersteller haben das Feature auf eigene Faust wieder hinzugefügt. Dies wurde hier nun mehrmals erwähnt. Keine Ahnung, warum du und auch andere das einfach mal komplett ignorieren. Was genau ist eure Mission?
Ich zitiere mal:
"Based on a variety of conversations with individuals I won’t name, it appears that the plan to have AVX-512 in Alder Lake was there from the beginning. It was working on early silicon, even as far as ES1/ES2 silicon, and was enabled in the firmware. Then for whatever reason, someone decided to remove that support from Intel’s Plan of Record (POR, the features list of the product).
By removing it from the POR, this means that the feature did not have to be validated for retail, which partly speeds up the binning and testing/validation process. As far as I understand it, the engineers working on the feature were livid. While all their hard work would be put to use on Sapphire Rapids, it still meant that Alder Lake would drop the feature and those that wanted to prepare for Alder Lake would have to remain on simulated support. Not only that, as we’ve seen since Architecture Day, it’s been a bit of a marketing headache. Whoever initiated that dropped support clearly didn’t think of how that messaging was going to down, or how they were going to spin it into a positive. For the record, removing support isn’t a positive, especially given how much hullaballoo it seems to have caused.
We’ve done some extensive research on what Intel has done in order to ‘disable’ AVX-512. It looks like that in the base firmware that Intel creates, there is an option to enable/disable the unit, as there probably is for a lot of other features. Intel then hands this base firmware to the vendors and they adjust it how they wish. As far as we understand, when the decision to drop AVX-512 from the POR was made, the option to enable/disable AVX-512 was obfuscated in the base firmware. The idea is that the motherboard vendors wouldn’t be able to change the option unless they specifically knew how to – the standard hook to change that option was gone.
However, some motherboard vendors have figured it out. In our discoveries, we have learned that this works on ASUS, GIGABYTE, and ASRock motherboards, however MSI motherboards do not have this option. It’s worth noting that all the motherboard vendors likely designed all of their boards on the premise that AVX-512 and its high current draw needs would be there, so when Intel cut it, it meant perhaps that some boards were over-engineered with a higher cost than needed. I bet a few weren’t happy."
Source: https://www.anandtech.com/show/1704...hybrid-performance-brings-hybrid-complexity/2
Eine ähnliche Geschichte gab es bei AMD mit den x470 und b450 Boards. Da haben die Hersteller auf eigene Faust PCIe 4.0 erlaubt und dann von AMD einen auf den Deckel bekommen, da die ordnunggemäße Funktionfähigkeit nicht garantiert werden konnte. Die mussten nicht nur die Änderungen wieder zurücknehmen, sondern hat AMD denen auch mit einer Abmahnung gedroht.
Siehe: Ryzen 3000: AMD mahnt Asus für PCI-E 4.0 auf B450- und X470-Boards ab, mehr Transparenz bei Overclocking gefordert
Nö. du hast nur einfach mal wieder überhaupt keine Ahnung, wovon du redest
"'Alder Lake Intel Hybrid Technology will not support Intel® AVX-512. ISA features such as Intel® AVX, AVX-VNNI, Intel® AVX2, and UMONITOR/UMWAIT/TPAUSE are supported' We all basically knew this. VNNI coming to normal AVX is for ML even in hybrid heterogeneous designs"
Zuletzt bearbeitet:
