bug#42686: closed (Update to linux-libre 5.7)

[GNU bug Tracking System]

Your message dated Wed, 5 Aug 2020 13:27:16 -0400
with message-id <20200805172716.GA8526@jasmine.lan>
and subject line Re: Update to linux-libre 5.7
has caused the debbugs.gnu.org bug report #42686,
regarding Update to linux-libre 5.7
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
42686: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42686
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Update to linux-libre 5.7 Date: Sun, 2 Aug 2020 18:43:56 -0400

The attached patch updates our default kernel to linux-libre 5.7.

Among other things, this will bring in-kernel WireGuard support,
multipath TCP, and USB4 (Thunderbolt).

I tested on x86_64 bare-metal and virtualized i686.

I'd like to push this as a "kernel-updates" branch and let Cuirass build
it. In the past, we always did this so that nobody had to build it
themselves. CI admins, can we do this? I don't have another way to test
for ARM platforms.

I have questions about some new features:

* Enable the compressed cache for swap pages by default? (ZSWAP_DEFAULT_ON)

Should we enable this? It seems useful and the compression algorithms
are known to be very fast. Are there any downsides?

* Enable the DMA-BUF userland memory heaps? This options creates per
heap chardevs in /dev/dma_heap/ which allows userspace to allocate
dma-bufs that can be shared between drivers. (DMABUF_HEAPS)

I don't really know what that means.

* Should USB4 (Thunderbolt) be built-in? Or a module?

0001-gnu-linux-libre-Update-to-5.7.12.patch
Description: Text document

signature.asc
Description: PGP signature

--- End Message ---

--- Begin Message --- Subject: Re: Update to linux-libre 5.7 Date: Wed, 5 Aug 2020 13:27:16 -0400

The CI server successfully built linux-libre 5.7 for x86_64, i686, and
aarch64:

http://ci.guix.gnu.org/search?query=spec%3Akernel-updates+linux-libre-5.7

I guess that it doesn't build kernels for armhf, since it appears that
nothing was attempted.

Anyways, I pushed the update as 843344273c6a587b8e6c84d8406500fd64d8908a

Please report any problems!

signature.asc
Description: PGP signature

--- End Message ---