From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: venture@google.com, "Peter Foley" <pefoley@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Foley" <pefoley@google.com>
Subject: Re: [PATCH v3] Don't require libcap-ng for virtfs support
Date: Thu, 04 May 2023 12:49:17 +0200 [thread overview]
Message-ID: <2765335.zQaF1C8VJ4@silver> (raw)
In-Reply-To: <20230503130757.863824-1-pefoley@google.com>
On Wednesday, May 3, 2023 3:07:56 PM CEST Peter Foley wrote:
> It's only required for the proxy helper.
>
> Add a new option for the proxy helper rather than enabling it
> implicitly.
>
> Change-Id: I95b73fca625529e99d16b0a64e01c65c0c1d43f2
> Signed-off-by: Peter Foley <pefoley@google.com>
> ---
LGTM now, queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
Best regards,
Christian Schoenebeck
> meson.build | 12 +++++++++---
> meson_options.txt | 2 ++
> scripts/meson-buildoptions.sh | 4 ++++
> 3 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index 77d42898c8..a46bc67cdb 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1759,12 +1759,17 @@ have_virtfs = get_option('virtfs') \
> error_message: 'virtio-9p (virtfs) requires Linux or macOS') \
> .require(targetos == 'linux' or cc.has_function('pthread_fchdir_np'),
> error_message: 'virtio-9p (virtfs) on macOS requires the presence of pthread_fchdir_np') \
> - .require(targetos == 'darwin' or (libattr.found() and libcap_ng.found()),
> - error_message: 'virtio-9p (virtfs) on Linux requires libcap-ng-devel and libattr-devel') \
> + .require(targetos == 'darwin' or libattr.found(),
> + error_message: 'virtio-9p (virtfs) on Linux requires libattr-devel') \
> .disable_auto_if(not have_tools and not have_system) \
> .allowed()
>
> -have_virtfs_proxy_helper = targetos != 'darwin' and have_virtfs and have_tools
> +have_virtfs_proxy_helper = get_option('virtfs_proxy_helper') \
> + .require(targetos != 'darwin', error_message: 'the virtfs proxy helper is incompatible with macOS') \
> + .require(have_virtfs, error_message: 'the virtfs proxy helper requires that virtfs is enabled') \
> + .disable_auto_if(not have_tools) \
> + .require(libcap_ng.found(), error_message: 'the virtfs proxy helper requires libcap-ng') \
> + .allowed()
>
> if get_option('block_drv_ro_whitelist') == ''
> config_host_data.set('CONFIG_BDRV_RO_WHITELIST', '')
> @@ -3911,6 +3916,7 @@ if have_block
> summary_info += {'Block whitelist (ro)': get_option('block_drv_ro_whitelist')}
> summary_info += {'Use block whitelist in tools': get_option('block_drv_whitelist_in_tools')}
> summary_info += {'VirtFS support': have_virtfs}
> + summary_info += {'VirtFS Proxy Helper support': have_virtfs_proxy_helper}
> summary_info += {'Live block migration': config_host_data.get('CONFIG_LIVE_BLOCK_MIGRATION')}
> summary_info += {'replication support': config_host_data.get('CONFIG_REPLICATION')}
> summary_info += {'bochs support': get_option('bochs').allowed()}
> diff --git a/meson_options.txt b/meson_options.txt
> index 2471dd02da..908b4b7fd9 100644
> --- a/meson_options.txt
> +++ b/meson_options.txt
> @@ -272,6 +272,8 @@ option('vhost_user_blk_server', type: 'feature', value: 'auto',
> description: 'build vhost-user-blk server')
> option('virtfs', type: 'feature', value: 'auto',
> description: 'virtio-9p support')
> +option('virtfs_proxy_helper', type: 'feature', value: 'auto',
> + description: 'virtio-9p proxy helper support')
> option('libvduse', type: 'feature', value: 'auto',
> description: 'build VDUSE Library')
> option('vduse_blk_export', type: 'feature', value: 'auto',
> diff --git a/scripts/meson-buildoptions.sh b/scripts/meson-buildoptions.sh
> index d4369a3ad8..3bb9dd3504 100644
> --- a/scripts/meson-buildoptions.sh
> +++ b/scripts/meson-buildoptions.sh
> @@ -176,6 +176,8 @@ meson_options_help() {
> printf "%s\n" ' vhost-vdpa vhost-vdpa kernel backend support'
> printf "%s\n" ' virglrenderer virgl rendering support'
> printf "%s\n" ' virtfs virtio-9p support'
> + printf "%s\n" ' virtfs-proxy-helper'
> + printf "%s\n" ' virtio-9p proxy helper support'
> printf "%s\n" ' vmnet vmnet.framework network backend support'
> printf "%s\n" ' vnc VNC server'
> printf "%s\n" ' vnc-jpeg JPEG lossy compression for VNC server'
> @@ -461,6 +463,8 @@ _meson_option_parse() {
> --disable-virglrenderer) printf "%s" -Dvirglrenderer=disabled ;;
> --enable-virtfs) printf "%s" -Dvirtfs=enabled ;;
> --disable-virtfs) printf "%s" -Dvirtfs=disabled ;;
> + --enable-virtfs-proxy-helper) printf "%s" -Dvirtfs_proxy_helper=enabled ;;
> + --disable-virtfs-proxy-helper) printf "%s" -Dvirtfs_proxy_helper=disabled ;;
> --enable-vmnet) printf "%s" -Dvmnet=enabled ;;
> --disable-vmnet) printf "%s" -Dvmnet=disabled ;;
> --enable-vnc) printf "%s" -Dvnc=enabled ;;
>
prev parent reply other threads:[~2023-05-04 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5706940.3l9IZQ4Y0r@silver>
2023-05-03 13:07 ` [PATCH v3] Don't require libcap-ng for virtfs support Peter Foley
2023-05-04 10:49 ` Christian Schoenebeck [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=2765335.zQaF1C8VJ4@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pefoley@google.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=venture@google.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).