Announcement

Collapse
No announcement yet.

KVM Virtualization With Linux 6.7 Adds LoongArch, Up To 4096 x86 vCPUs

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

  • KVM Virtualization With Linux 6.7 Adds LoongArch, Up To 4096 x86 vCPUs

    Phoronix: KVM Virtualization With Linux 6.7 Adds LoongArch, Up To 4096 x86 vCPUs

    The Kernel-based Virtual Machine (KVM) changes were sent out on Thursday for the Linux 6.7 merge window...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    4096 x86 CPUs aka Nuclear Fission.

    Comment


    • #3
      Obligatory reference to xkcd and 4,096 CPU's: https://xkcd.com/619/

      Comment


      • #4
        Originally posted by DanL View Post
        Obligatory reference to xkcd and 4,096 CPU's: https://xkcd.com/619/
        What's really missing from Linux kernel these days? Userland is another land

        Comment


        • #5
          Originally posted by timofonic View Post

          What's really missing from Linux kernel these days? Userland is another land
          Full bottom up HDR(10,12,etc) support. Can't have it without proper driver support. It's near the point now where if you go looking to buy a new monitor it's almost always going to have (bad) HDR10 even near the low end. It and color profiles are no longer just in the realm of content creators any more. Dell Ultrasharps now sell at $300 and up while $200 monitors at Walmart now have (bad) HDR10 support. Bleed through is awful on the things, but they still have it. HDR can't be ignored any longer. (Not 100% clear about which drivers have HDR support at this point, some? one? all?, point is the feature isn't anywhere near complete yet.)
          Last edited by stormcrow; 03 November 2023, 06:14 PM.

          Comment


          • #6
            Originally posted by stormcrow View Post

            Full bottom up HDR(10,12,etc) support. Can't have it without proper driver support. It's near the point now where if you go looking to buy a new monitor it's almost always going to have (bad) HDR10 even near the low end. It and color profiles are no longer just in the realm of content creators any more. Dell Ultrasharps now sell at $300 and up while $200 monitors at Walmart now have (bad) HDR10 support. Bleed through is awful on the things, but they still have it. HDR can't be ignored any longer. (Not 100% clear about which drivers have HDR support at this point, some? one? all?, point is the feature isn't anywhere near complete yet.)
            The Kernel has HDR support, you can use with MPV for example. What we don't have is a Wayland protocol for it. So it's user land problem

            Comment


            • #7
              Originally posted by ranixon View Post

              The Kernel has HDR support, you can use with MPV for example. What we don't have is a Wayland protocol for it. So it's user land problem
              Someone else proved my point! Shamanic magic! Thanks!

              Comment


              • #8
                Originally posted by timofonic View Post

                Someone else proved my point! Shamanic magic! Thanks!
                No, it's really missing the point. Users don't care who's to blame. Linux the operating system is missing proper HDR support. "The Kernel" which part? Which drivers? Who knows? Who cares? All GPU drivers need support, not just one or two. Yes, so do the DEs and window managers. Like I said. Missing the point.

                Comment


                • #9
                  Originally posted by stormcrow View Post

                  No, it's really missing the point. Users don't care who's to blame. Linux the operating system is missing proper HDR support. "The Kernel" which part? Which drivers? Who knows? Who cares? All GPU drivers need support, not just one or two. Yes, so do the DEs and window managers. Like I said. Missing the point.
                  You can't blame separate projects with different responsibilities, you need to blame relevant software. Ignorance isn't an excuse. If user are ignorants, they just will use the easiest thing and just a few others will be more savvy.
                  Last edited by timofonic; 03 November 2023, 09:18 PM.

                  Comment


                  • #10
                    Originally posted by timofonic View Post

                    You can't blame separate projects with different responsibilities, you need to blame relevant software. Ignorance isn't an excuse. If user are ignorants, they just will use the easiest thing and just a few others will be more savvy.
                    Problem is that Linux isn't just a hobby project anymore. Everything (kernel, utils, init, driver, desktops) are managed by groups/companies, they're not just indies in their spare time now. But they're not communicating, which puts them at a severe disadvantage with macOS and Windows where all projects that make up the OS are in very tight communication with one another and arent even afraid to have entire projects rewritten if it makes things better. Windows has had several major component rewrites in it's history and nobody even noticed. People chirp about systemd adoption and compositor rewrites, Windows has had this stuff happen in the background for years and it's been a complete non-issue, same with macOS going from Xorg to Quartz. Nobody even paid attention because the corporation held all responsibility for the transfer and nobody outside the company even had to flinch.
                    This is the problem, these "separate projects" shouldn't be separate in the first place, they should be working together more closely. Instead we still have this hodgepodge mess of poorly integrated components that offer a poorer experience than the all-in-one integrated experiences you get from complete OSes from corporations. You cannot admit to these projects being poorly integrated and in the same breath blame the user for criticizing this model.

                    Comment

                    Working...
                    X