From: David Heidelberg <david@ixit.cz>
To: Vivek Goyal <vgoyal@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: dri-devel@lists.freedesktop.org, helen.koike@collabora.com,
Al Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
virtualization@lists.linux-foundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
wsa+renesas@sang-engineering.com, akpm@linux-foundation.org
Subject: Re: [RESEND v2 PATCH] init/do_mounts.c: add virtiofs root fs support
Date: Mon, 27 Feb 2023 21:55:57 +0100 [thread overview]
Message-ID: <cee2e3ea-14a6-c51f-7ce6-6a67dabff6f1@ixit.cz> (raw)
In-Reply-To: <Y/zxO9PMaES8SenN@redhat.com>
Thank you all!
We'll drop this patch in next MesaCI kernel uprev without this patch!
David
On 27/02/2023 19:06, Vivek Goyal wrote:
> On Mon, Feb 27, 2023 at 10:53:45AM -0500, Stefan Hajnoczi wrote:
>> On Fri, Feb 24, 2023 at 03:37:51PM +0100, David Heidelberg wrote:
>>> From: Stefan Hajnoczi <stefanha@redhat.com>
>>>
>>> Make it possible to boot directly from a virtiofs file system with tag
>>> 'myfs' using the following kernel parameters:
>>>
>>> rootfstype=virtiofs root=myfs rw
>>>
>>> Booting directly from virtiofs makes it possible to use a directory on
>>> the host as the root file system. This is convenient for testing and
>>> situations where manipulating disk image files is cumbersome.
>>>
>>> Reviewed-by: Helen Koike <helen.koike@collabora.com>
>>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>> ---
>>> v2: added Reviewed-by and CCed everyone interested.
>>>
>>> We have used this option in Mesa3D CI for testing crosvm for
>>> more than one years and it's proven to work reliably.
>>>
>>> We are working on effort to removing custom patches to be able to do
>>> automated apply and test of patches from any tree.
>>>
>>> https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/.gitlab-ci/crosvm-runner.sh#L85
>>> init/do_mounts.c | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>> Vivek, do you remember where we ended up with boot from virtiofs? I
>> thought a different solution was merged some time ago.
> We merged a patch from Christoph Hellwig to support this.
>
> commit f9259be6a9e7c22d92e5a5000913147ae17e8321
> Author: Christoph Hellwig <hch@lst.de>
> Date: Wed Jul 14 16:23:20 2021 -0400
>
> init: allow mounting arbitrary non-blockdevice filesystems as root
>
> Now one should be able to mount virtiofs using following syntax.
>
> "root=myfs rootfstype=virtiofs rw"
>
> IIUC, this patch should not be required anymore.
>
> Thanks
> Vivek
>
>> There is documentation from the virtiofs community here:
>> https://virtio-fs.gitlab.io/howto-boot.html
>>
>> Stefan
>>
>>> diff --git a/init/do_mounts.c b/init/do_mounts.c
>>> index 811e94daf0a8..11c11abe23d7 100644
>>> --- a/init/do_mounts.c
>>> +++ b/init/do_mounts.c
>>> @@ -578,6 +578,16 @@ void __init mount_root(void)
>>> printk(KERN_ERR "VFS: Unable to mount root fs via SMB.\n");
>>> return;
>>> }
>>> +#endif
>>> +#ifdef CONFIG_VIRTIO_FS
>>> + if (root_fs_names && !strcmp(root_fs_names, "virtiofs")) {
>>> + if (!do_mount_root(root_device_name, "virtiofs",
>>> + root_mountflags, root_mount_data))
>>> + return;
>>> +
>>> + panic("VFS: Unable to mount root fs \"%s\" from virtiofs",
>>> + root_device_name);
>>> + }
>>> #endif
>>> if (ROOT_DEV == 0 && root_device_name && root_fs_names) {
>>> if (mount_nodev_root() == 0)
>>> --
>>> 2.39.1
>>>
>
--
David Heidelberg
Consultant Software Engineer
prev parent reply other threads:[~2023-02-27 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 14:37 David Heidelberg
2023-02-27 15:53 ` Stefan Hajnoczi
2023-02-27 18:06 ` Vivek Goyal
2023-02-27 20:55 ` David Heidelberg [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=cee2e3ea-14a6-c51f-7ce6-6a67dabff6f1@ixit.cz \
--to=david@ixit.cz \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=helen.koike@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa+renesas@sang-engineering.com \
/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
all inboxes | Powered by JetHome®