From: Josh Triplett <josh@joshtriplett.org>
To: Changbin Du <changbin.du@gmail.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH v3 0/3] 9p: add support for root file systems
Date: Mon, 14 Jun 2021 01:57:54 -0700 [thread overview]
Message-ID: <YMcaEq95T+1GxZz2@localhost> (raw)
In-Reply-To: <20210606230922.77268-1-changbin.du@gmail.com>
On Mon, Jun 07, 2021 at 07:09:19AM +0800, Changbin Du wrote:
> Just like cifs and nfs, this short series enables rootfs support for 9p.
> Bellow is an example which mounts v9fs with tag 'r' as rootfs in qemu
> guest via virtio transport.
>
> $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 \
> -virtfs local,path=$rootfs_dir,mount_tag=r,security_model=passthrough,id=r \
> -kernel /path/to/linux/arch/x86/boot/bzImage -nographic \
> -append "root=/dev/v9fs v9fsroot=r,trans=virtio rw console=ttyS0 3"
Rather than inventing a pseudo-device /dev/v9fs for this, would it
potentially work to use the existing rootfstype and rootflags options
for this? rootfstype already determines what filesystem should be used
to mount the root, and rootflags already provides options for that
filesystem.
For instance, for the above example:
rootfstype=9p root=r rootflags=trans=virtio
That would require a bit of fiddling to make rootfstype=9p allow a root
that's just the mount_tag. If that isn't an option, then even with
root=/dev/v9fs I think it still makes sense to use the existing
rootflags for "trans=virtio" rather than creating a new "v9fsroot"
option for that.
- Josh Triplett
next prev parent reply other threads:[~2021-06-14 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 23:09 [PATCH v3 0/3] 9p: add support for root file systems Changbin Du
2021-06-06 23:09 ` [PATCH v3 1/3] " Changbin Du
2021-06-07 1:06 ` kernel test robot
2021-06-14 1:09 ` Changbin Du
2021-06-06 23:09 ` [PATCH v3 2/3] 9p: doc: move to a new dedicated folder Changbin Du
2021-06-06 23:09 ` [PATCH v3 3/3] 9p: doc: add v9fsroot description Changbin Du
2021-06-06 23:45 ` [PATCH v3 0/3] 9p: add support for root file systems Dominique Martinet
2021-06-14 8:57 ` Josh Triplett [this message]
2021-06-14 9:01 ` Dominique Martinet
2021-06-14 9:19 ` Josh Triplett
2021-06-20 3:36 ` Changbin Du
2021-06-20 4:16 ` Dominique Martinet
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=YMcaEq95T+1GxZz2@localhost \
--to=josh@joshtriplett.org \
--cc=asmadeus@codewreck.org \
--cc=changbin.du@gmail.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=v9fs-developer@lists.sourceforge.net \
/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