qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, stefanha@redhat.com, vgoyal@redhat.com
Cc: virtio-fs@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] Add virtio-fs (experimental)
Date: Fri, 23 Aug 2019 18:56:55 +0100	[thread overview]
Message-ID: <20190823175657.12085-1-dgilbert@redhat.com> (raw)

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

Hi,
  This pair of patches adds the core of the virtio-fs support to qemu;
it's marked experimental since the kernel patch and spec changes aren't
in yet; but they're bubbling along.

  While the spec change is still in progress; the ID number is already
reserved.

  A future set of patches will add the optional DAX mapping support.

  The actual qemu change is pretty minimal, since it's really only
a virtio device with some queues.

Some links:
  Mailing list: https://www.redhat.com/mailman/listinfo/virtio-fs
  Dev tree: Including filesystem daemon: https://gitlab.com/virtio-fs/qemu
  kernel: https://gitlab.com/virtio-fs/linux
  virtio spec changes: https://lists.oasis-open.org/archives/virtio-dev/201908/msg00104.html

v2:
  Renamed num_queues to num_request_queues
  Add a not-reached assert to vuf_handle_output
  Kill the one bit of notification queue off
  Use the same trick as vhost-user-scsi to calculate the number
    of vectors for the PCI device

Dr. David Alan Gilbert (2):
  virtio: add vhost-user-fs base device
  virtio: add vhost-user-fs-pci device

 configure                                   |  13 +
 hw/virtio/Makefile.objs                     |   2 +
 hw/virtio/vhost-user-fs-pci.c               |  85 ++++++
 hw/virtio/vhost-user-fs.c                   | 297 ++++++++++++++++++++
 include/hw/virtio/vhost-user-fs.h           |  45 +++
 include/standard-headers/linux/virtio_fs.h  |  41 +++
 include/standard-headers/linux/virtio_ids.h |   1 +
 7 files changed, 484 insertions(+)
 create mode 100644 hw/virtio/vhost-user-fs-pci.c
 create mode 100644 hw/virtio/vhost-user-fs.c
 create mode 100644 include/hw/virtio/vhost-user-fs.h
 create mode 100644 include/standard-headers/linux/virtio_fs.h

-- 
2.21.0



             reply	other threads:[~2019-08-23 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 17:56 Dr. David Alan Gilbert (git) [this message]
2019-08-23 17:56 ` [Qemu-devel] [PATCH v2 1/2] virtio: add vhost-user-fs base device Dr. David Alan Gilbert (git)
2019-08-26 15:32   ` Cornelia Huck
2019-09-05 15:05     ` Dr. David Alan Gilbert
2019-08-27  2:39   ` [Qemu-devel] [Virtio-fs] " piaojun
2019-09-03 17:58     ` Dr. David Alan Gilbert
2019-08-23 17:56 ` [Qemu-devel] [PATCH v2 2/2] virtio: add vhost-user-fs-pci device Dr. David Alan Gilbert (git)
2019-08-26 15:35   ` Cornelia Huck
2019-09-03 17:55     ` Dr. David Alan Gilbert
2019-08-23 17:57 ` [Qemu-devel] [Virtio-fs] [PATCH v2 0/2] Add virtio-fs (experimental) Dr. David Alan Gilbert

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=20190823175657.12085-1-dgilbert@redhat.com \
    --to=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@redhat.com \
    --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).