- Joined
- Mar 13, 2021
- Messages
- 483 (0.35/day)
Processor | AMD 7600x |
---|---|
Motherboard | Asrock x670e Steel Legend |
Cooling | Silver Arrow Extreme IBe Rev B with 2x 120 Gentle Typhoons |
Memory | 4x16Gb Patriot Viper Non RGB @ 6000 30-36-36-36-40 |
Video Card(s) | XFX 6950XT MERC 319 |
Storage | 2x Crucial P5 Plus 1Tb NVME |
Display(s) | 3x Dell Ultrasharp U2414h |
Case | Coolermaster Stacker 832 |
Power Supply | Thermaltake Toughpower PF3 850 watt |
Mouse | Logitech G502 (OG) |
Keyboard | Logitech G512 |
This is the real reason.Could they also be doing this because HT has been vulnerable to attacks in the past? Is this still a viable question with HT on, or has this problem been fixed up via CPU micro codes?
HT in the enterprise environment has proved time and again in recent times to be one of if not the easiest attack vectors currently known especially with it being used to bypass virtualisation security by being able to access whatever is running on the other thread on the same CPU when its not from the same VM.
AMD have already got offerings in via Zen 4c (EPYC 9754S) that suits these use cases to please major cloud providers/heavy virtualisation users.
XMP is another bucket of worms. If the compatibility is poor the user experience may be riddled with problems (hello AM4, not sure about modern Intel).
Another consumer unfriendly area, although it improved, but still unfriendly.
XMP is an Intel standard that AMD "Supports" but I doubt they have put the a lot of resource into XMP as they have developing their own standard EXPO. Also with memory speeds and timings getting faster and tighter the differences in memory controller performance and optimization highlights how a "one size fits all" approach to memory isnt working as it once was.