When you finish celebrating Linux turning 30, try new Linux 5.14, says Linus Torvalds Linux overlord Linus Torvalds has released version 5.14 of the Linux kernel. "So I realize you must all still be busy with all the galas and fancy balls and all the other 30th anniversary events, but at some point you must be getting tired of the constant glitz, the fireworks, and the champagne," wrote Torvalds in his weekly …
Speaking of Intel, version 5.14 of the kernel adds more support for Chipzilla's Alder Lake platform that puts multiple core types onto a single die and prioritises workloads depending on their needs.
When version 5.14 of the kernel recognises and takes stealthy advantage of Intel platforms that put multiple core needs onto a single die prioritising workloads depending on the type of performance operation, are Spectre and Meltdown type attack vectors more enhanced and hardened/reinforced and re-engineered to react somewhat differently from the expected system programming norms.
I don't imagine Intel thinking that is additional support for their platforms though, whenever it renders their core source foundations compromisable, for it is a catastrophic systemic flaw in their structural base architecture which all but invites remote random renegade rogue access to cores and anonymous third party exploitation of executive functions.
Let's wait & see before casting stones, amfM. No point in going off half cocked. .... jake
Quite so, jake, there is no great rush. Time is something there is always a great deal more of to allow and encourage ...... Proper Preparation and Positive Planning Prevents Piss Poor Performance Permitting Prime Prize Plum Penetrations and Perfect Private Protocolled Pursuit of Public Parametered Projects and Pirate ProgramMING Productions for Pumping and Pimping in Presentations to Populations Puzzled by Progress and Prisonered with Pathetic Past Postings Profiling and Pioneering with Pilots Practised in Plush Promising Programs and Prolifically Painful Pogroms.
Psst . .... :-) some folk are not into casting stones, jake, whenever their forte and raison d'être is hurling GIGAntic FCUKing Rocks.
So the solution to Spectre is to run trusted code on trusted cores with trusted caches where everyone is good and totally trustworthy, where no one will be peeking at the caches. And then all the general riff-raff will be kept on the disreputable ghetto cores where they can only savage each other.
So more isolation using more cores is the optimal software workaround to what is really a hardware design flaw.
AMD/Intel/ARM should fix the problem in hardware like the LibreSoC people are doing:
https://libre-soc.org/3d_gpu/requirements_specification/
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
