From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Cc: linux-kernel@vger.kernel.org, konrad.wilk@oracle.com,
boris.ostrovsky@oracle.com, ericvh@gmail.com,
rminnich@sandia.gov, lucho@ionkov.net,
v9fs-developer@lists.sourceforge.net, groug@kaod.org
Subject: Re: [PATCH v4 0/7] Xen transport for 9pfs frontend driver
Date: Thu, 16 Mar 2017 07:19:00 +0100 [thread overview]
Message-ID: <5d250095-b899-2449-6930-a96a0800cfe6@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1703151219330.4807@sstabellini-ThinkPad-X260>
On 15/03/17 20:23, Stefano Stabellini wrote:
> Hi all,
>
> This patch series implements a new transport for 9pfs, aimed at Xen
> systems.
>
> The transport is based on a traditional Xen frontend and backend drivers
> pair. This patch series implements the frontend, which typically runs in
> a regular unprivileged guest.
>
> I also sent a series that implements the backend in userspace in QEMU,
> which typically runs in Dom0 (but could also run in a another guest).
>
> The frontend complies to the Xen transport for 9pfs specification
> version 1, available here:
>
> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob_plain;f=docs/misc/9pfs.markdown;hb=HEAD
>
>
> Changes in v4:
> - code style improvements
> - use xenbus_read_unsigned when possible
> - do not leak "versions"
> - introduce BUILD_BUG_ON
> - introduce rwlock to protect the xen_9pfs_devs list
> - add review-by
>
> Changes in v3:
> - add full copyright header to trans_xen.c
> - rename ring->ring to ring->data
> - handle gnttab_grant_foreign_access errors
> - remove ring->bytes
> - wrap long lines
> - add reviewed-by
>
> Changes in v2:
> - use XEN_PAGE_SHIFT instead of PAGE_SHIFT
> - remove unnecessary initializations
> - fix error paths
> - fix memory allocations for 64K kernels
> - simplify p9_xen_create and p9_xen_close
> - use virt_XXX barriers
> - set status = REQ_STATUS_ERROR inside the p9_xen_response loop
> - add in-code comments
>
>
> Stefano Stabellini (7):
> xen: import new ring macros in ring.h
> xen: introduce the header file for the Xen 9pfs transport protocol
> xen/9pfs: introduce Xen 9pfs transport driver
> xen/9pfs: connect to the backend
> xen/9pfs: send requests to the backend
> xen/9pfs: receive responses
> xen/9pfs: build 9pfs Xen transport driver
>
> include/xen/interface/io/9pfs.h | 40 ++++
> include/xen/interface/io/ring.h | 131 ++++++++++
> net/9p/Kconfig | 8 +
> net/9p/Makefile | 4 +
> net/9p/trans_xen.c | 513 ++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 696 insertions(+)
> create mode 100644 include/xen/interface/io/9pfs.h
> create mode 100644 net/9p/trans_xen.c
I strongly recommend running checkpatch.pl to avoid style problems. This
will save us some more rounds, I guess: there are multiple style
violations in the patches which are not related to the header import
from Xen.
Juergen
next prev parent reply other threads:[~2017-03-16 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 19:23 Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 1/7] xen: import new ring macros in ring.h Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 2/7] xen: introduce the header file for the Xen 9pfs transport protocol Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 3/7] xen/9pfs: introduce Xen 9pfs transport driver Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 4/7] xen/9pfs: connect to the backend Stefano Stabellini
2017-03-16 6:31 ` Juergen Gross
2017-03-16 18:04 ` Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 5/7] xen/9pfs: send requests " Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 6/7] xen/9pfs: receive responses Stefano Stabellini
2017-03-15 19:23 ` [PATCH v4 7/7] xen/9pfs: build 9pfs Xen transport driver Stefano Stabellini
2017-03-16 6:19 ` Juergen Gross [this message]
2017-03-16 17:47 ` [PATCH v4 0/7] Xen transport for 9pfs frontend driver Stefano Stabellini
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=5d250095-b899-2449-6930-a96a0800cfe6@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ericvh@gmail.com \
--cc=groug@kaod.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=rminnich@sandia.gov \
--cc=sstabellini@kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=xen-devel@lists.xenproject.org \
/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®