unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: Linux-libre-4.15 and the NVMe module
Date: Mon, 29 Jan 2018 09:18:17 -0500	[thread overview]
Message-ID: <87fu6obvfa.fsf@netris.org> (raw)

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

             reply	other threads:[~2018-01-29 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 14:18 Mark H Weaver [this message]
2018-01-29 17:09 ` Linux-libre-4.15 and the NVMe module ng0
2018-01-30 10:12 ` Mark H Weaver
2018-01-31 13:37   ` Ludovic Courtès
2018-01-30 11:07 ` Danny Milosavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu6obvfa.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).