Linux Kernel 4.10 Officially Released With Virtual GPU Support (softpedia.com)
"Linus Torvalds announced today the general availability of the Linux 4.10 kernel series, which add a great number of improvements, new security features, and support for the newest hardware components," writes Softpedia. prisoninmate quotes their report:
Linux kernel 4.10 has been in development for the past seven weeks, during which it received a total of seven Release Candidate snapshots that implemented all the changes that you'll soon be able to enjoy on your favorite Linux-based operating system... Prominent new features include virtual GPU (Graphics Processing Unit) support, new "perf c2c" tool that can be used for analysis of cacheline contention on NUMA systems, support for the L2/L3 caches of Intel processors (Intel Cache Allocation Technology), eBPF hooks for cgroups, hybrid block polling, and better writeback management. A new "perf sched timehist" feature has been added in Linux kernel 4.10 to provide detailed history of task scheduling, and there's experimental writeback cache and FAILFAST support for MD RAID5... Ubuntu 17.04 (Zesty Zapus) could be the first stable OS to ship with Linux 4.10.
It required 13,000 commits, plus over 1,200 merges, Linus wrote in the announcement, adding "On the whole, 4.10 didn't end up as small as it initially looked."
It required 13,000 commits, plus over 1,200 merges, Linus wrote in the announcement, adding "On the whole, 4.10 didn't end up as small as it initially looked."
...that we'll finally get a Nouveau driver that isn't a crash-prone piece of crap?
Il n'y a pas de Planet B.
Well, even the newest kernels (I can vouch for 4.9.x at least) have no systemd requirement. I run that and am still happily systemd-free.
The bigger question I have is re. virtual GPU: would it finally be possible to use Wayland in a QEMU-based VM? It would be nice to get see how that works--but still I wait for Wayland to have some ability to work across networks.
Looks like you can get near-native performance even though you're sharing hardware. With this maybe instead of a dual boot PC you can have a dual VM PC, one runs Linux and the other Windows and both at near native performance and you don't have to dedicate a graphics card. That sounds like a real gateway drug, use Linux for the desktop and the games that run on it but be able to switch to your Wintendo and play that one must-have game your friends want. That said right now it looks like an an Intel tech, did anyone see anything about AMD/nVidia support? Because sharing that Intel iGPU wasn't really what I'm looking for....
Live today, because you never know what tomorrow brings
Running 4.9 on 4 physical machines in my home. And also running 4.9 on over a dozen VMs in a datacenter without systemd.
There are a few distributions that don't push it down your throat. There are even a few others that offer (optional) alternative kernels and init systems.
Personally I use funtoo.
Take a look at www.without-systemd.org for more.
Can someone link to a concise discussion of what this does and some use cases? Thanks.
SystemD is in userspace. There are no dependencies for SystemD in the kernel.
Now I hate SystemD far more than most due to it causing actual failures for me in production, but spreading disinformation about it is dishonest.
Well, now we are on Windows version 10. At this rate we'll be eventually at Windows version . 000...0001
No, but it would help you run Windows CAD packages inside a Windows VM and get near native GPU performance both in the Windows VM and Linux host. vGPU lets you share a single compatible GPU across multiple VMs running on the same system. This way each VM can benefit from full hardware accelerated 3D rendering as well as access to OpenCL and/or CUDA even though only a single physical GPU is present in the system.
Wine wouldn't benefit because it already has direct access to the GPU as long as it's associated with the host system, it's issues are caused by imperfect compatibility between how Windows does something, and how WINE implemented it. For example, Wine translates Direct3D calls into OpenGL calls which can then be run natively in Linux, but if the translation isn't perfect, or a certain Direct3D call hasn't been implemented in WINE yet, then the program is going to behave differently than it should.
How about native ZFS support?
"I say we take off, nuke the site from orbit. It's the only way to be sure."