4 ms·

Oh wow. When did this change? I vaguely seem to remember that as recently as Windows 7 (or was it 8.0?) there was trouble with AVX2 or something, but I can't fi

Oh wow. When did this change? I vaguely seem to remember that as recently as Windows 7 (or was it 8.0?) there was trouble with AVX2 or something, but I can't find the info anywhere at the moment.

JoshTriplett 10y ago
An OS can still use xsave incorrectly, such as by hardcoding the expected size rather than detecting it at runtime, or by getting some aspect of the CPUID leaf 0xd enumeration wrong. I wouldn't find it surprising if an initial implementation got one of the details wrong, resulting in a bug that wouldn't manifest until the next time the xsave layout changed.
- amelius 10y ago
  The CPU designers could have protected against this by randomly fluctuating the size of the xsave'd data.
  - monocasa 10y ago
    At the cost of extra bandwidth and interrupt latency.
    - amelius 10y ago
      Yes, but only marginally if they changed the size only 1 out of 1000 times.
      - spdionis 10y ago
        Adding complexity (that could result in bugs) in the hope to prevent bugs by bad usage of the interface is usually a bad idea.
MaulingMonkey 10y ago
Perhaps you're thinking of this debugger issue? https://randomascii.wordpress.com/2013/03/11/should-this-windows-7-bug-be-fixed/ https://randomascii.wordpress.com/2013/03/11/should-this-win...
- wfunction 10y ago
  Ah yes, good find, I believe this was one of them! I don't remember if there were more though, there might have been.