From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <marius@gnu.org>
Cc: 60129@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#60129] [PATCH 0/2] VM-optimized Linux-Libre variant
Date: Sat, 17 Dec 2022 17:32:09 +0100 [thread overview]
Message-ID: <87r0wygfee.fsf@gnu.org> (raw)
In-Reply-To: <20221216221147.13945-1-marius@gnu.org> (Marius Bakke's message of "Fri, 16 Dec 2022 23:11:47 +0100")
Hello!
(Cc: kernel “team”. I’m guessing that the whole team may well
unanimously welcome you on board. :-))
Marius Bakke <marius@gnu.org> skribis:
> The kernel is tailored towards server workloads running on a VPS, but
> should work fine as a default for "guix system vm", etc.
For a second I wondered whether we should change
‘virtualized-operating-system’ to put it in the ‘kernel’ field
unconditionally. But it’s probably not a good idea because we have
system tests targeting specific kernels, and because users may want to
test “actual” kernels in QEMU.
> | benchmark | linux-libre | linux-libre-virtual |
> |-------------------------|---------------|---------------------|
> | guix size | 101.4 MiB | 36.2 MiB |
Wo0t!
> activation: Firmware activation handles missing support in kernel.
> gnu: Add linux-libre-virtual.
You may want a better-informed opinion on the linux-libre bits, but
otherwise LGTM!
Ludo’.
next prev parent reply other threads:[~2022-12-17 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 22:11 [bug#60129] [PATCH 0/2] VM-optimized Linux-Libre variant Marius Bakke
2022-12-16 22:15 ` [bug#60129] [PATCH 1/2] activation: Firmware activation handles missing support in kernel Marius Bakke
2022-12-16 22:15 ` [bug#60129] [PATCH 2/2] gnu: Add linux-libre-virtual Marius Bakke
2022-12-16 23:40 ` [bug#60129] [PATCH 1/2] activation: Firmware activation handles missing support in kernel Tobias Geerinckx-Rice via Guix-patches via
2022-12-17 16:10 ` Marius Bakke
2022-12-17 16:32 ` Ludovic Courtès [this message]
2022-12-23 18:14 ` [bug#60129] [PATCH 0/2] VM-optimized Linux-Libre variant Leo Famulari
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=87r0wygfee.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60129@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=marius@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).