- Joined
- May 31, 2016
- Messages
- 4,325 (1.50/day)
- Location
- Currently Norway
System Name | Bro2 |
---|---|
Processor | Ryzen 5800X |
Motherboard | Gigabyte X570 Aorus Elite |
Cooling | Corsair h115i pro rgb |
Memory | 16GB G.Skill Flare X 3200 CL14 @3800Mhz CL16 |
Video Card(s) | Powercolor 6900 XT Red Devil 1.1v@2400Mhz |
Storage | M.2 Samsung 970 Evo Plus 500MB/ Samsung 860 Evo 1TB |
Display(s) | LG 27UD69 UHD / LG 27GN950 |
Case | Fractal Design G |
Audio Device(s) | Realtec 5.1 |
Power Supply | Seasonic 750W GOLD |
Mouse | Logitech G402 |
Keyboard | Logitech slim |
Software | Windows 10 64 bit |
AS always you have missed the conversation we been having here before you showed up. It is well known that Intel been the one developers for software turn into and used features they have offered. That's why software has been developed with Intel's TSX not AMD's ASF due to the fact Intel's been a leader for some time and has some sort of advantage. You repeating what I wrote dudeIntel implemented TSX in Haswell (and it was broken), it is implemented in a fixed way in Skylake - and used in one of the KASLR-breaking vulnerabilities which again prompts for disabling it. AMD has (proposed) ASF extension as counterpart that have not actually been implemented in anything so far.
It is not about prefering Intel's extension but using what CPU manufacturer has implemented in actual products (= can be used). TSX exists and works in an actual product, ASF does not.
And yes, developers preferred Intel's feature. Even though it didn't work and now it is disabled. Just like Metroid mentioned. ASF works but has not been used. Hopefully this will change soon and I hope developers will give it a shot.