From: George Dunlap <george.dunlap@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] tools: specifically enable VirtFS in Linux QEMU builds
Date: Thu, 6 Sep 2018 13:51:31 +0100 [thread overview]
Message-ID: <fcbb6a64-1a6c-1bf8-6ea6-8489e83e9be6@citrix.com> (raw)
In-Reply-To: <20180906120636.38754-1-paul.durrant@citrix.com>
On 09/06/2018 01:06 PM, Paul Durrant wrote:
> 9pfs support has been a documented feature since Xen 4.9, but QEMU will
> not be built with backend support unless libcap and libattr dev packages
> are installed.
>
> This patch modifies the README to call out those packages as pre-requisites
> for Linux builds and specifically enables VirtFS in the configure line
> for QEMU so that an error message is displayed if they are missing.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> ---
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> Cc: George Dunlap <George.Dunlap@eu.citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Julien Grall <julien.grall@arm.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Stefano Stabellini <sstabellini@kernel.org>
> Cc: Tim Deegan <tim@xen.org>
> Cc: Wei Liu <wei.liu2@citrix.com>
> ---
> README | 2 ++
> tools/Makefile | 11 +++++++++++
> 2 files changed, 13 insertions(+)
>
> diff --git a/README b/README
> index 4b95b21c7b..1a4e4b2c1b 100644
> --- a/README
> +++ b/README
> @@ -56,6 +56,8 @@ provided by your OS distributor:
> greater.
> * Development install of GLib v2.0 (e.g. libglib2.0-dev)
> * Development install of Pixman (e.g. libpixman-1-dev)
> + * Development install of libcap (e.g. libcap-dev) [Linux only]
> + * Development install of libattr (e.g. libattr1-dev) [Linux only]
> * pkg-config
> * bridge-utils package (/sbin/brctl)
> * iproute package (/sbin/ip)
> diff --git a/tools/Makefile b/tools/Makefile
> index 67977ad850..e74efb8a6e 100644
> --- a/tools/Makefile
> +++ b/tools/Makefile
> @@ -216,6 +216,11 @@ else
> QEMU_XEN_ENABLE_DEBUG :=
> endif
>
> +#
> +# 9pfs support is a documented feature but it depends on a QEMU with
> +# VirtFS enabled. However VirtFS is a Linux-only option so only enable
> +# it for Linux builds.
> +#
> subdir-all-qemu-xen-dir: qemu-xen-dir-find
> unset MAKELEVEL; \
> if test -d $(QEMU_UPSTREAM_LOC) ; then \
> @@ -232,10 +237,16 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
> else \
> enable_trace_backend='' ; \
> fi ; \
> + if [ "$(CONFIG_Linux)" = "y" ]; then \
> + enable_virtfs='--enable-virtfs' ; \
> + else \
> + enable_virtfs='' ; \
> + fi ; \
9pfs is still a reasonably "niche" feature; I don't think we want to
force people to enable it if they don't expect to use it.
Is it the case that if we have libcap and libattr, that qemu will enable
9pfs automatically? If so we should just document that.
Another option would be to have "--enable-9pfs" option in the tools
configure, which would then pass this on to qemu (and thus fail if the
requisite librares aren't present), but I'm not sure if having a load of
"--enable-*" at the top level is really what we want for this.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-06 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 12:06 [PATCH] tools: specifically enable VirtFS in Linux QEMU builds Paul Durrant
2018-09-06 12:51 ` George Dunlap [this message]
2018-09-06 13:08 ` Paul Durrant
2018-09-06 18:11 ` Stefano Stabellini
2018-09-07 8:35 ` Paul Durrant
2018-09-07 14:57 ` Roger Pau Monné
2018-09-07 15:25 ` George Dunlap
2018-09-07 15:27 ` Paul Durrant
2018-09-07 16:18 ` Ian Jackson
2018-09-07 16:20 ` Paul Durrant
2018-09-07 16:55 ` Stefano Stabellini
2018-09-07 16:57 ` Stefano Stabellini
2018-09-07 17:00 ` Paul Durrant
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=fcbb6a64-1a6c-1bf8-6ea6-8489e83e9be6@citrix.com \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=paul.durrant@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).