Skip to main content



 
A lot of the tweaks are deferrals because the contexts are getting too large. The FPU is a few registers on plain x86 but add in SSE and suddenly you are talking another 8 128 bit registers. On ARM's SVE the SIMD context can get up to 8kb of data! Debug registers can become similarly huge, especially if the hardware supports lots of watch and breakpoints.



 
#Linux #kernel 5.0-rc2 is out. I'd give it the codename 'normal' ;-) Quotes from the announcement (lore.kernel.org/lkml/CAHk-=wic…) will explain: "[…] rc2 looks pretty normal […] Things look pretty normal […] As to actual changes: all looks fairly normal […] Go test, Linus […]"




 
That's unusual: The #Linux stable and longterm #kernel 4.20.2, 4.19.5 and 4.14.93 (released an hour ago) mark devm_memremap_pages() as well as hmm_devmem_{add, add_resource}() as EXPORT_SYMBOL_GPL. Thus proprietary drivers won't be able to use those functions anymore.

To clarify the "[…] won't be able to use […]" bit here's a quote from https://www.kernel.org/doc/html/latest/kernel-hacking/hacking.html?highlight=export_symbol_gpl#export-symbol-gpl: "[…] symbols exported by EXPORT_SYMBOL_GPL() can only be seen by modules with a MODULE_LICENSE() that specifies a GPL compatible license. […]".

For completeness: Last #LKML discussion about these patches before they got merged to mainline before #Linux version 5.0-rc1 recently: https://lore.kernel.org/lkml/154275557457.76910.16923571232582744134.stgit@dwillia2-desk3.amr.corp.intel.com/t/#mf921de6121863f733a6b12e348f4013a56e53233 Commits for 4.19.y:
* https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=0f1a62e0737a9a1c09d4cc86162724656db9eb70
* https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=b30ea244cf3e1f086da008fe6fa0278154f49244









 
TWIMC: Patches got applied to the docs tree now \o/ Jon didn't like the commit msg and rewrote it (thx), but well, was my first non-trivial #linux #kernel patch, things like that can happen.

Finally can remove this from my todo list....

lore.kernel.org/lkml/201901081…


 
Posted the second version of my documentation patch (which became a patch-set) that hopefully makes it easier to decode why your #Linux #kernel was tainted. This (like so often…) got way bigger than anticipated, but well, afaics it was worth the trouble. lore.kernel.org/lkml/201901081…



 


 
@kernellogger
Why is there so little information about X1 to X10? Wikipedia at least mentions X10, but what about the previous versions?

no idea, sorry. Guess some kind of combination of "nobody really cares" and "ancient past"
@allo



 
Tomeu Vizoso – A #Panfrost milestone "[…] proper implementation of the winsys abstraction that makes use of ARM's kernel driver […] we can now run applications on GBM, from demos such as kmscube and glmark2 to compositors such as Weston[…]" #arm #mali
blog.tomeuvizoso.net/2019/01/a-panf…



 
Compile from a up2date #git checkout if you want to run a #Linux mainline #kernel. Do not rely on release patches and tarballs, as they might miss important fixes; luckily in the case of #Linux 5.0-rc1 it's only relevant for a few archs.

End of PSA ;-)

lore.kernel.org/lkml/CAHk-=wiH…




 
First prerelease of #Linux #kernel 5.0 is out: "[…] The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0. […] So go wild. Make up […]" lore.kernel.org/lkml/CAHk-=wgK…





 
Virtio_Blk finally supports discard and write zeroes in the #Linux mainline #kernel (thus it will be in 4.21, which might be called 5.0 instead). That will make it easier to shrink VM images by getting rid of data that got deleted (like TRIM does for SSDs)
git.kernel.org/torvalds/c/1f2…