From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
linux-arm-kernel@lists.infradead.org
Cc: 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 09:46:24 +0530 [thread overview]
Message-ID: <8f512add-b78f-49df-9239-274e7a9558ea@arm.com> (raw)
In-Reply-To: <cd8cc649-c4e9-4868-b68a-6a9de72b32fe@app.fastmail.com>
On 16/07/26 5:01 PM, Arnd Bergmann wrote:
> On Thu, Jul 16, 2026, at 13:01, Krzysztof Kozlowski wrote:
>> On 16/07/2026 12:02, Anshuman Khandual wrote:
>>> Commit d521c4ca039f ("arm64: defconfig: Switch Ethernet drivers to modules")
>>> had changed 9P and virtio-9P support from built-in to modular instead. This
>>> breaks simple kvmtool boots using a 9P root filesystem without an initramfs
>>> , because the kernel must mount root filesystem before it can load the 9P
>>
>>
>> And that commit explained you must use initramfs. Nothing got broken,
>> because there was never a promise that a recent, virtualized environment
>> must work on defconfig without initramfs.
>>
>> 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,
Actually that is a very normal use case particularly with KVM tool.
> 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.
Alright - fair 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.
The following sequence does indeed solve this problem for now.
make mrproper
make defconfig
make kvm_guest.config
prev parent reply other threads:[~2026-07-17 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 10:02 [PATCH] arm64/defconfig: Restore built-in 9P rootfs support Anshuman Khandual
2026-07-16 11:01 ` Krzysztof Kozlowski
2026-07-16 11:31 ` Arnd Bergmann
2026-07-17 4:16 ` Anshuman Khandual [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=8f512add-b78f-49df-9239-274e7a9558ea@arm.com \
--to=anshuman.khandual@arm.com \
--cc=alexandre.belloni@bootlin.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