From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: virtio-fs@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtiofsd: add man page
Date: Wed, 4 Sep 2019 19:10:30 +0100 [thread overview]
Message-ID: <20190904181030.GA26826@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190903153539.GM2744@work-vm>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On Tue, Sep 03, 2019 at 04:35:39PM +0100, Dr. David Alan Gilbert wrote:
> * Stefan Hajnoczi (stefanha@redhat.com) wrote:
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > ---
> > Makefile | 7 +++
> > contrib/virtiofsd/virtiofsd.texi | 85 ++++++++++++++++++++++++++++++++
> > 2 files changed, 92 insertions(+)
> > create mode 100644 contrib/virtiofsd/virtiofsd.texi
> >
> > diff --git a/Makefile b/Makefile
> > index a3dfdd6fa8..cc18025753 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -334,6 +334,9 @@ DOCS+=docs/qemu-cpu-models.7
> > ifdef CONFIG_VIRTFS
> > DOCS+=fsdev/virtfs-proxy-helper.1
> > endif
> > +ifdef CONFIG_LINUX
>
> Is there a reason that's CONFIG_LINUX not CONFIG_VHOST_USER_FS ?
> (Although I guess it's guest vs daemon so the two are independent?)
Yes, this is virtiofsd, not vhost-user-fs-pci. We don't have a
CONFIG_VIRTIOFSD.
> > +DOCS+=contrib/virtiofsd/virtiofsd.1
> > +endif
> > ifdef CONFIG_TRACE_SYSTEMTAP
> > DOCS+=scripts/qemu-trace-stap.1
> > endif
> > @@ -834,6 +837,9 @@ ifdef CONFIG_VIRTFS
> > $(INSTALL_DIR) "$(DESTDIR)$(mandir)/man1"
> > $(INSTALL_DATA) fsdev/virtfs-proxy-helper.1 "$(DESTDIR)$(mandir)/man1"
> > endif
> > +ifdef CONFIG_LINUX
> > + $(INSTALL_DATA) contrib/virtiofsd.1 "$(DESTDIR)$(mandir)/man1"
>
> I had to fix that to contrib/virtiofsd/virtiofsd.1 to get make install
> happy.
Thanks for spotting it!
> > +@c man begin DESCRIPTION
> > +
> > +Share a host directory tree with a guest through a virtio-fs device. This
> > +program is a vhost-user backend that implements the virtio-fs device. Each
> > +virtio-fs device instance requires its own virtiofsd process.
> > +
> > +This program is designed to work with QEMU's @code{--device vhost-user-fs-pci}
>
> Should we include the -pci there?
>
> (Merged with the path fix above)
We could also be more general and say "vhost-user virtio-fs device" to
avoid the issue.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-09-04 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 10:41 [Qemu-devel] [PATCH] virtiofsd: add man page Stefan Hajnoczi
2019-08-29 17:36 ` [Qemu-devel] [Virtio-fs] " Liu Bo
2019-09-03 15:35 ` [Qemu-devel] " Dr. David Alan Gilbert
2019-09-04 18:10 ` Stefan Hajnoczi [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=20190904181030.GA26826@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-fs@redhat.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;
as well as URLs for NNTP newsgroup(s).