Linux Kernel 6.9

https://lkml.org/lkml/2024/5/12/224

"6.9 is now out," Linus Torvalds posted on the Linux kernel mailing list

Linux 6.9 "has a number of exciting features and improvements for those habitually updating to the newest version." he said.

Highlights of Linux kernel 6.9 include

>Rust support

on AArch64 (ARM64) architectures, support for the Intel FRED (Flexible Return and Event Delivery) mechanism for improved low-level event delivery, support for AMD SNP (Secure Nested Paging) guests, and a new dm-vdo (virtual data optimizer) target in device mapper for inline deduplication, compression, zero-block elimination, and thin provisioning.

Linux kernel 6.9 also supports the Named Address Spaces feature in GCC (GNU Compiler Collection) that allows the compiler to better optimize per-CPU data access, adds initial support for FUSE passthrough to allow the kernel to serve files from a user-space FUSE server directly, adds support for the Energy Model to be updated dynamically at run time, and introduces a new LPA2 mode for ARM 64-bit processors...

"Rust language has been updated to version 1.76.0 in Linux 6.9," according to the article. And Linus Torvalds shared one more details on the Linux kernel mailing list.

"I now have a more powerful arm64 machine (thanks to Ampere), so the last week I've been doing almost as many arm64 builds as I have x86-64, and that should obviously continue during the upcoming merge window too." he said.

A Conspiracy Theorist Is Talking Shirt $21.68

The Kind of Tired That Sleep Won’t Fix Shirt $21.68

A Conspiracy Theorist Is Talking Shirt $21.68

  1. 1 week ago
    Anonymous

    >"Rust language has been updated to version 1.76.0 in Linux 6.9," according to the article. And Linus Torvalds
    what a homosexual he became

    • 1 week ago
      Anonymous

      >almost 500000 lines of code added
      Linux is troonbloat

      I'm switching to bsd

  2. 1 week ago
    Anonymous

    >almost 500000 lines of code added
    Linux is troonbloat

  3. 1 week ago
    Anonymous

    Does it fix how 6.8.9 broke a shitload of games??

    • 1 week ago
      Anonymous

      they wont say

      did the game was brokken due to x.x.9 though?
      so 6.9.1 might work where 6.8.9 doesnt

    • 1 week ago
      Anonymous

      Arch+LTS kernel and you will never have to deal with instability.
      I don't even restart my workstation, unless a major security kernel patch was added, or I had to because the power was out.
      This happens once every few months.
      I don't play games though.

    • 1 week ago
      Anonymous

      like what?

    • 1 week ago
      Anonymous

      Arch+LTS kernel and you will never have to deal with instability.
      I don't even restart my workstation, unless a major security kernel patch was added, or I had to because the power was out.
      This happens once every few months.
      I don't play games though.

      kek the absolute state of troonix

  4. 1 week ago
    Anonymous

    nice

  5. 1 week ago
    Anonymous

    Linus was asked if he would code in rust now.
    His answer was: "god no !"

    No further questions, I rest my case

    • 1 week ago
      Anonymous

      he doenst have to code in Rust himself he just supports Rust so that Linux developers can use it

      • 1 week ago
        Anonymous

        except noone uses this, some trannies tinkertroon, but the fact that you need to manually go out of your way to find and install a rust driver because none of them are accepted into kernel tree directly, means that noone will care.

        • 1 week ago
          Anonymous

          Prepare the COPE for when the first driver gets in tree.
          Let me help:
          >They gave the traan troon treen a driver to shut them up. No one will enable it in their builds.
          I can't help you with the next level of COPE when more Rust code will be added I'm afraid.

          • 1 week ago
            Anonymous

            Which hardware development company is gonna do this? Trannies cannot even rewrite LLVM in Rust, and they will develop hardware now?

          • 1 week ago
            Anonymous

            As I told you, "meh Rust traan troon treen can't do anything" talking points won't work for long.
            Prepare the COPE from now.
            Drivers are already being written in Rust.
            And yes, some are being written by people employed directly by the hardware vendors.
            And drivers are just the start.

          • 1 week ago
            Anonymous

            I'm asking which company is doing this now, driver written by literally who will never make it into kernel. Even USEFUL things like OpenZFS cannot make it into Linux, but somehow troonyware will, 2 more weeks right?

          • 1 week ago
            Anonymous

            >2 more weeks right?
            2 more years.
            That will be enough for every single "rust traan troon treen" IQfytard talking point of today to be rendered void.
            I'm sure you will latch onto some new ones by then though, since you don't want to prepare some COPE yourself.

          • 1 week ago
            Anonymous

            ok make sure the driver is actually relevant

          • 1 week ago
            Anonymous

            Good. You're learning fast, and already made use of my suggested COPE here

            Prepare the COPE for when the first driver gets in tree.
            Let me help:
            >They gave the traan troon treen a driver to shut them up. No one will enable it in their builds.
            I can't help you with the next level of COPE when more Rust code will be added I'm afraid.

          • 1 week ago
            Anonymous

            I compile Linux at home so if the driver isn't relevant and won't be in my build I literally do not care.
            Now tell us your guess, will it be novideo that does this first? Good thing I don't use troony hardware.

          • 1 week ago
            Anonymous

            >Now tell us your guess, will it be novideo that does this first? Good thing I don't use troony hardware.
            I hate to break it to you. But David Airlie is probably the biggest Rust fan among kernel devs. So your COPE will have to include not using a GPU at all. lol.

          • 1 week ago
            Anonymous

            >noveau
            good thing I don't use novideo card

          • 1 week ago
            Anonymous

            LMAO.
            Of course you have no idea who David Airlie is.
            I would have mentioned DRM, but I was concerned you would think it's Digital Rights Management.
            I didn't want to embarrass you. I'm that nice.

          • 1 week ago
            Anonymous

            ok waiting for DRM to be rewritten in Rust, just 2 more weeks right?

          • 1 week ago
            Anonymous

            You write like a bot written by a middle school kid.
            At least use different "jokes".

          • 1 week ago
            Anonymous

            2 more weeks until you make a response in good faith, right?

            [...]

          • 1 week ago
            Anonymous

            bot comment confirmed

    • 1 week ago
      Anonymous

      Wait, if Linus doesn't want to write kernel code in Rust, then why the frick did he add it?

      he doenst have to code in Rust himself he just supports Rust so that Linux developers can use it

      But why? He's the boss, isn't he?

      • 1 week ago
        Anonymous

        >Wait, if Linus doesn't want to write kernel code in Rust, then why the frick did he add it?
        Maybe to get rusttroons off his back? They're incredibly annoying and persistent shills.

      • 1 week ago
        Anonymous

        >then why the frick did he add it?
        pressure from the Linux Foundation most likely. This Rust saga has basically been Linus and co doing the absolute bare minimum to include 'Rust support', but refuse to actually use it.

      • 1 week ago
        Anonymous

        why did he add the troony coc

  6. 1 week ago
    Anonymous

    thanks but I'll stick with 6.8.8

  7. 1 week ago
    Anonymous

    All I care about is if it's faster than 6.8

  8. 1 week ago
    Anonymous

    why was it (technically) needed for Linux to do anything special in order to "support" Rust anyway? I mean if you can compile something into a native binary, then isn't that already enough to be able to write a device driver or a kernel module or whatever in that specific language?

    • 1 week ago
      Anonymous

      because kernel modules work by patching Linux at runtime

      • 1 week ago
        Anonymous

        lol.
        I hope this is a joke, or a deliberate misdirection.
        I hate to think that it was the result of a special ignorance+moronation combo.

    • 1 week ago
      Anonymous

      A couple of links to feed your intellectual curiosity.
      The second one is maybe a bit too technical, especially when it comes to the details.
      https://github.com/Rust-for-Linux/linux/issues/2
      https://lwn.net/Articles/967049/
      So the answer to your question could be yes for a trivial use-case. But that's not what's going on here.
      What's going on here is preparing for full blown support from both sides.
      And this effort is funded by the way:
      https://rust-for-linux.com/sponsors

      • 1 week ago
        Anonymous

        Thank you.

  9. 1 week ago
    Anonymous

    Debian Stable and never updooting

  10. 1 week ago
    Anonymous

    @100448571 (You)
    I accept your concession. I was about to explain what runtime linking is but I realized I already wrote it in previous post.

  11. 1 week ago
    Anonymous

    linux is pozzed since linus took a brake after sending a distress signal then everyone forgot about it

  12. 1 week ago
    Anonymous

    Rust was added in the kernel by microsoft to make the builds longer.

    • 1 week ago
      Anonymous

      It was added by glowBlack folk to hide backdoors in rust's unreadable syntax

  13. 1 week ago
    Anonymous

    The kernel has fallen

  14. 1 week ago
    Anonymous

    I'm never upgrading from v6.6.6

Your email address will not be published. Required fields are marked *