From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Linux-libre-4.15 and the NVMe module Date: Mon, 29 Jan 2018 09:18:17 -0500 Message-ID: <87fu6obvfa.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42382) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1egAGu-0001I3-Aq for guix-devel@gnu.org; Mon, 29 Jan 2018 09:19:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1egAGo-0006bK-Kt for guix-devel@gnu.org; Mon, 29 Jan 2018 09:18:56 -0500 Received: from world.peace.net ([50.252.239.5]:48196) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1egAGo-0006b5-Fn for guix-devel@gnu.org; Mon, 29 Jan 2018 09:18:50 -0500 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Hello Guix, I've pushed a new 'kernel-updates' branch that includes the update to linux-libre-4.15, and asked Hydra to build it. However, I haven't yet pushed this to 'master' because of a complication. At present, all of our kernel configurations have CONFIG_BLK_DEV_NVME=m which results in an "nvme.ko" module, and this module is included in the list of modules to be copied to our 'base-initrd' and loaded during early boot. Unfortunately, it seems that in linux-libre-4.15, we must now have CONFIG_BLK_DEV_NVME=y (built-in) if we wish to keep CONFIG_NVM=y (Open-Channel SSD target support), which we've had enabled in our kernel configurations since 4.4. CONFIG_NVM cannot be made modular, and in 4.15 it now depends on CONFIG_BLK_DEV_NVME=y. Since I don't see a nice way in our current 'base-initrd' implementation to conditionally include "nvme.ko" depending on the kernel configuration, I simply removed "nvme.ko" from the list of modules, and changed all of our kernel configurations to have CONFIG_BLK_DEV_NVME=y. While I was at it, I updated our older kernel configurations to the current point releases, using "make oldconfig". My main motivation for doing this was to explicitly show in our config files that we've enabled the mitigations for meltdown and spectre. Any comments on this approach? Other suggestions? Mark