Linux Kills Ancient x86 Fallbacks
unknownuniverse.uk
As Linux 7.2 makes the Time Stamp Counter mandatory, we look at why dropping legacy x86 fallback timing code is long overdue.

Linux 7.2 has landed, dragging x86 timing clean out of the nineties by making the Time Stamp Counter mandatory.

I wrote up a quick article on why ditching those ancient legacy fallbacks is good housekeeping, plus a few other bits like cache-aware scheduling and memory tweaks worth noting.

Is anyone still using legacy hardware? If so, what do you use it for?

  • db2@lemmy.world
    11·
    5 hours ago

    Some features are compromised by the requirement to keep this old code, though I’m not qualified to say to what extent.

    “Trust me bro”

    Who’s still using a Cyril 6x86 that isn’t doing it for personal/recreational reasons?

    In your estimation clearly nobody. You’re evading the question of why they should be artificially forced to use outdated software by denying enthusiasts who want to use a kernel built by an enthusiast and then by a bunch of enthusiasts for enthusiasts exist. 🤦‍♂️

    • brucethemoose@lemmy.world
      2·
      5 hours ago

      I’m sorry, but I have a bit more trust in the Linux kernel maintainers on the technicals of this issue than you or I.

      I do know enough to know that a Cyril 6x86 is problematic to use with many modern applications. I find it hard to believe anyone using one needs a modern kernel feature for something, and any other PC is unavailable.

      I mean, at the very least, I think they’d need another PC to build a custom kernel themselves? Can you even build Linux 7.1 on that system now?