From: Alyssa Ross <hi@alyssa.is>
To: colbyt <colby@colbyt.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH v3] vm: optional 16K-page guest kernel builds
Date: Fri, 31 Jul 2026 16:04:41 +0200 [thread overview]
Message-ID: <877bmb2r2e.fsf@alyssa.is> (raw)
In-Reply-To: <20260730193541.1928150-1-colby@colbyt.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
colbyt <colby@colbyt.com> writes:
> KVM hosts with a 16K stage-2 granule (Apple Silicon machines running
> upstream kernels, NVIDIA GB10) can only run guests whose kernel is built
> with ARM64_16K_PAGES. Add an optional kernelPageSize argument to the app
> and net VM kernel builds; the default is unchanged. A 16K-page guest
> Image built this way has booted to a full session under a 16K host here
> since June without issues on my side.
> ---
> v3/v2: no code change — drop a stray in-body From line that would have
> misattributed authorship when applied.
>
> Following up on the offer in my July 7 mail, as a standalone patch now
> that the nixpkgs update brings Linux 7.1. The config delta is five
> lines; the edit (an argument defaulting to today's behavior) is a
> proposal — happy to rework it if you'd rather structure it differently,
> e.g. hang it off a single shared helper instead of two arguments.
My instinct is that we should just always use a 16K page kernel on
aarch64 hosts. AIUI the main reason most Linux distributions don't is
to retain compatibility with binaries that may assume only 4K alignment
is needed, but on the Spectrum host we should never be running binaries
we didn't build ourselves.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2026-07-31 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 19:20 [PATCH] vm: optional 16K-page guest kernel builds colbyt
2026-07-30 19:28 ` [PATCH v2] " colbyt
2026-07-30 19:35 ` [PATCH v3] " colbyt
2026-07-31 14:04 ` Alyssa Ross [this message]
2026-08-01 18:40 ` colby
2026-08-03 12:49 ` Alyssa Ross
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877bmb2r2e.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=colby@colbyt.com \
--cc=devel@spectrum-os.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://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
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 NNTP newsgroup(s).