From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
Eric Biggers <ebiggers@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/defconfig: Restore built-in 9P rootfs support
Date: Fri, 17 Jul 2026 18:14:32 +0100 [thread overview]
Message-ID: <feec0cf1-2d9c-4074-a56c-ee91bee9080f@sirena.org.uk> (raw)
In-Reply-To: <cd8cc649-c4e9-4868-b68a-6a9de72b32fe@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Thu, Jul 16, 2026 at 01:31:17PM +0200, Arnd Bergmann wrote:
> On Thu, Jul 16, 2026, at 13:01, Krzysztof Kozlowski wrote:
> > You fully control your software, so just build initramfs which is
> > absolutely trivial and we all moved on to that for arm64 long time ago.
> I still regularly boot KVM guests on arm64 without an initramfs,
> but I just use 'make kvm_guest.config', which turns on all the
> commonly used virtio drivers as built-in. I wouldn't call
> 9pfs root trivial without initramfs, configuring 9p built-in
> is already complicated enough.
> So I agree we don't need this patch, but there is a trivial
> workaround for Anshuman in case he wants to avoid doing this.
Though watch out for the fact that this currently disables KVM which
isn't so helpful on the multiple architectures that have nested guest
support. I'll send a patch for that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-17 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 10:02 Anshuman Khandual
2026-07-16 11:01 ` Krzysztof Kozlowski
2026-07-16 11:31 ` Arnd Bergmann
2026-07-17 4:16 ` Anshuman Khandual
2026-07-17 17:14 ` Mark Brown [this message]
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=feec0cf1-2d9c-4074-a56c-ee91bee9080f@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=ebiggers@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox