From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] qemu-options.hx: 9p: clarify -virtfs vs. -fsdev
Date: Mon, 20 Apr 2020 17:42:26 +0200 [thread overview]
Message-ID: <20200420174226.69807b11@bahia.lan> (raw)
In-Reply-To: <208f1fceffce2feaf7c900b29e326b967dce7762.1585661532.git.qemu_oss@crudebyte.com>
On Tue, 31 Mar 2020 15:23:38 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> The docs are ambiguous about the difference (or actually their
> equality) between options '-virtfs' vs. '-fsdev'. So clarify that
> '-virtfs' is actually just a convenience shortcut for its
> generalized form '-fsdev' in conjunction with '-device virtio-9p-pci'.
>
> And as we're at it, also be a bit more descriptive what 9pfs is
> actually used for.
>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
Applied to 9p-next.
> qemu-options.hx | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 962a5ebaa6..fd3830c6cd 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -1542,9 +1542,17 @@ SRST
> ``-virtfs proxy,sock_fd=sock_fd,mount_tag=mount_tag [,writeout=writeout][,readonly]``
> \
> ``-virtfs synth,mount_tag=mount_tag``
> - Define a new filesystem device and expose it to the guest using a
> - virtio-9p-device. The general form of a Virtual File system
> - pass-through options are:
> + Define a new virtual filesystem device and expose it to the guest using
> + a virtio-9p-device (a.k.a. 9pfs), which essentially means that a certain
> + directory on host is made directly accessible by guest as a pass-through
> + file system by using the 9P network protocol for communication between
> + host and guests, if desired even accessible, shared by several guests
> + simultaniously.
> +
> + Note that ``-virtfs`` is actually just a convenience shortcut for its
> + generalized form ``-fsdev -device virtio-9p-pci``.
> +
> + The general form of pass-through file system options are:
>
> ``local``
> Accesses to the filesystem are done by QEMU.
prev parent reply other threads:[~2020-04-20 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 13:23 [PATCH] qemu-options.hx: 9p: clarify -virtfs vs. -fsdev Christian Schoenebeck
2020-03-31 15:27 ` Cornelia Huck
2020-03-31 15:41 ` Christian Schoenebeck
2020-03-31 16:05 ` Markus Armbruster
2020-03-31 16:10 ` Cornelia Huck
2020-04-01 9:08 ` Christian Schoenebeck
2020-04-20 15:42 ` Greg Kurz [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=20200420174226.69807b11@bahia.lan \
--to=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.