Skip to main content

[bookmark=]Vulkan RPI4 vulkan driver, v3dv, got merged recently on mesa master, and from today, you can track their evolution on @igalia # # [/bookmark]

Among the overlayfs changes merged for # # 5.10 (… ) are preparations for unprivileged ovl mounts and a "volatile" mode; the latter can improve performance for certain container setups by disabling sync on the overlay. (… ).

[bookmark=]We are pleased to announce a significant milestone for the Vulkan driver that we have been developing , in collaboration with the Raspberry Pi Foundation... # # # [/bookmark]

hackbyte reshared this.

[bookmark=]TIL modern Linuxes let you dynamically turn hyperthreading on and off:
echo off > /sys/devices/system/cpu/smt/control[/bookmark]

Looks like a few machines already stopped booting # ISOs or installations that used to start fine; seems those machines already got a # update to make # # deny boot stacks that are vulnerable to # # (CVE-2020-10713, published late June).


[bookmark=]"This patch series adds DAX support to virtiofs filesystem. This allows bypassing guest page cache and allows mapping host page cache directly in guest address space."[/bookmark]

[bookmark=]Interested in the results of the survey for # 2020? We've now made them available on our blog. 🙂 Go check them out! 👇
LPC 2020 Survey Results

[bookmark=]Here's the Linux kernel vulnerability disclosure process I described based on the experience of reporting a few bugs, could have been useful here.…[/bookmark]

A # employee states their graphics drv will remain incompatible to the recently released # # 5.9 for another month:…

Guess that might be due to to a patch set from C. Hellwig that was discussed here and is in 5.9:…

uh-oh! damn, who needs their proprietary crap.

# # 5.9.1, 5.8.16, 5.4.72, 4.19.152, 4.14.202, 4.9.240, & 4.4.240 are out and among other important fixes contain patches to fix the # vulnerability "#".

Thx @gregkh for maintaining these version lines & for taking care of it on a Sat. morning!

# 5.9.1 and 5.8.16 are out and among other important fixes contain patches to fix the # vulnerability "#".

# 5.4.72, 4.19.152, 4.14.202, 4.9.240, and 4.4.240 are expected to follow soon and will fix the security issue, too.

[bookmark=]This pair of blog posts that blows up the idea that you can benchmark by running a warm-up period and then taking the last N results without looking at the underlying data are some of the best performance blog posts I’ve ever seen:……

Plot of benchmark that slows down after warm-up period and additionally has a spike sometime after being warmed up.
Plot of benchmark that shows no steady state regardless of warmup time.
Plot of benchmark that becomes more divergent over time as more warmup is done. [/bookmark]

[bookmark=]I'll be giving a talk version of my article (…) at Open Source Summit Eu.
Lot's of diagrams to try to make it less complex. [/bookmark]

[bookmark=]awesome work!

Specification and verification in the field: Applying formal methods to BPF just-in-time compilers in the Linux kernel…


New # and # # # with the fixes for the # vulnerability "#" are now up for testing.

"[…] Responses should be made by Sun, 18 Oct 2020 09:04:25 +0000. Anything received after that time might be too late. […]" (that's for 5.9.1-rc1)

Highlights from the main # merge for # # 5.10:

* support for the display pipeline found in the # (and thus the #)

* Improvements for #'s RDNA2 (aka Navi2x)

* more preps. for the Gen12 GPU in # Rocket Lake


[bookmark=]I am really happy to see the Linux kernel support for AWS Nitro Enclaves land in Linus' tree today ⬇️. This is part of practicing "upstream first" # development, which I have found to be really important for Linux. [/bookmark]