Linux Kernel Gets Mitigations For TSX Aync Abort Plus Another New Issue: iITLB Multihit

[uid313]

There is nothing saying it is a fully new microarchitecture. It is not the same, that's true, but there is nothing saying it is a full redesign.

In general, a full architecture redesign is a big, complex thing like the one AMD did for ryzen. You don't pull it off in a year.

Yes, it is complex and no, you don't pull it off in a year, which is why this is Intel's first new microarchitecture since Skylake which was released in 2015 (4 years ago).
All processors prior to Ice Lake are optimizations of the Skylake architecture.

[starshipeleven]

Yes, it is complex and no, you don't pull it off in a year, which is why this is Intel's first new microarchitecture since Skylake which was released in 2015 (4 years ago).
All processors prior to Ice Lake are optimizations of the Skylake architecture.

I still don't think it is redesigned from scratch.

[rogerx]

Linux Kernel Intel TSX description, "auto if TSX is in use but it should be used on safe platforms" is somewhat confusing.

As most Linux Kernel code help descriptions are rather confusingly written; after re-reading several times, the help description for "auto" seems to imply there is a white and black listing hard-coded within the kernel sources, describing safe platforms and unsafe platforms.

Ah, Wikipedia is your friend! -> "Transactional Synchronization Extensions"
https://en.wikipedia.org/wiki/Transa...ion_Extensions

Briefly states some of the unsafe CPU platforms.

Ah Ha! Bingo! Reading /usr/src/linux/Documentation/admin-guide/hw-vuln/tsx_async_abort.rst provides elaborate explanation along with accessing relevant sysfs info!