Announcement

Collapse
No announcement yet.

Linux 5.16 Released With Many Intel & AMD Additions, Memory Folios, AMX, FUTEX2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Nocifer
    replied
    Originally posted by shmerl View Post

    Yeah, I didn't know that either. Apparently there is no good solution for this (at least now?). Proton might use it, but Wine won't. At least it's good to know there are very few cases when it's actually useful. And Wine staging still has esync so far.
    Apparently Valve and Collabora have been consistently funneling their efforts towards implementing and upstreaming futex_waitv for some time now, and apparently they know what they're doing since, due to their previous efforts, Wine has already transitioned from a mostly useless theoretical concept to a workable solution that's bound to change the Linux ecosystem; which means that apparently futex_waitv is already a good solution (predictable, since it's an evolution of the fsync concept and fsync is already good for many games, despite what that Wine dev was trying to say).

    So apparently we should maybe start treating Valve and Collabora as the authorities-that-be on Wine development in place of the original Wine team, because the former apparently care about evolving Wine into a proper real-world solution that solves real-world use cases (even if they only care due to their desire to make it into a profitable product) while the latter are apparently growing more and more comparable to the GNU purists, systemd haters and the various other anachronistic entities that plague Linux these days. If we relied on them and their concepts of what's worthy to be merged and what isn't, we'd still be "playing" DX11 games in single digit framerates. Bah.

    Please, do note that the bitter sarcasm is aimed not at you but at the Wine devs. Back when I told you (don't know if you remember our discussion) that I wasn't expecting futex_waitv support to be merged in Wine before at least both kernel 5.16 and Wine 7.0 were out of the door, I certainly wasn't expecting for it to be blocked from being merged indefinitely by the Wine devs due to Reasons™ - i.e. just as they've done with DXVK.

    Leave a comment:


  • Amano
    replied
    Maybe phoronix should remove the WINE reference in the article and change it to Proton

    Leave a comment:


  • Linuxxx
    replied
    Originally posted by shmerl View Post

    Yeah, I didn't know that either. Apparently there is no good solution for this (at least now?). Proton might use it, but Wine won't. At least it's good to know there are very few cases when it's actually useful. And Wine staging still has esync so far.
    Except the fact that Esync destroys consistent frametimes & makes shader-compile stutter unbearable; e.g. Battlefield 1, Dishonored 2, Batman - Arkham Knight, S.T.A.L.K.E.R. - Anomaly, etc.

    At least the Lutris-GE builds are already shipping the necessary patches for Fsync, which any sane person already gravitated towards years ago anyway, so upstream WINE's gatekeeper CodeWeavers can carry on caring about their paying Mactard customers!

    Leave a comment:


  • partcyborg
    replied
    Originally posted by Danny3 View Post

    Luckily the 5.16 kernel can be installed manually from that link or easier with Ubuntu Mainline Kernel Install third party too, but still some badly designed software like AMD proprietary drivers might refuse to install if it's not the original kernel version that Ubuntu 22.04 came with.
    For that case it's important that Ubuntu comes with an up-to-date kernel as possible.
    What? are you talking about the amdpro proprietary graphics drivers? Because those are entirely in userland, and are therefore essentially kernel agnostic. I'm not aware of any AMD closed source kernel modules.

    Leave a comment:


  • shmerl
    replied
    Originally posted by CochainComplex View Post

    shmerl THX for the interrogation very surprising. I thought it was the wine community pushing for in tree acceptance.
    Yeah, I didn't know that either. Apparently there is no good solution for this (at least now?). Proton might use it, but Wine won't. At least it's good to know there are very few cases when it's actually useful. And Wine staging still has esync so far.

    Leave a comment:


  • CochainComplex
    replied
    Originally posted by geearf View Post

    Wow I did not expect that either. Thanks for the link and Shmerl for asking all that info!
    shmerl THX for the interrogation very surprising. I thought it was the wine community pushing for in tree acceptance.

    Leave a comment:


  • geearf
    replied
    Originally posted by ihatemichael View Post
    Sounds like Wine won't be using futex2?

    https://bugs.winehq.org/show_bug.cgi?id=50281
    Wow I did not expect that either. Thanks for the link and Shmerl for asking all that info!

    Leave a comment:


  • birdie
    replied
    A human readable changelog: https://kernelnewbies.org/Linux_5.16

    nouveau has seen some changes but they are kinda smallish.
    Last edited by birdie; 10 January 2022, 01:05 PM. Reason: adding nouveau changelog

    Leave a comment:


  • dawid.mlyn
    replied
    Originally posted by ihatemichael View Post
    Sounds like Wine won't be using futex2?

    https://bugs.winehq.org/show_bug.cgi?id=50281
    Yeah, at least not in time for Wine 7.x and Ubuntu 22.x. Lets hope they will add it before the next LTS release in 2024. Wine 9.x name looks so cool and it will be the thing by then ;-)

    Leave a comment:


  • cytomax55
    replied
    People running Ubuntu should not be caring about the latest and greatest.... Either accept the older and more stable or hop on a distro that runs more modern stuff.... You can't have both

    Leave a comment:

Working...
X