From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: Andrew Jones <drjones@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: arm/aarch64: allow enable-seccomp
Date: Fri, 2 Oct 2015 16:02:12 +0200 [thread overview]
Message-ID: <20151002140212.GA25464@vader> (raw)
In-Reply-To: <1443628758-26038-1-git-send-email-drjones@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2627 bytes --]
On Wed, Sep 30, 2015 at 11=59=18AM -0400, Andrew Jones wrote:
> This is a revert of ae6e8ef11e6cb, but with a bit of refactoring,
> and also specifically adding arm/aarch64, rather than all
> architectures. Currently, libseccomp code appears to also support
> mips, ppc, and s390. We could therefore allow qemu to enable
> seccomp for those platforms as well, with additional configure
> patches, given they're tested and proven to work.
>
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
> Depends on
> http://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg00191.html
>
> configure | 32 +++++++++++++++++++++++++-------
> 1 file changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/configure b/configure
> index f14454e691b36..2d993bf210b56 100755
> --- a/configure
> +++ b/configure
> @@ -1870,16 +1870,34 @@ fi
> # libseccomp check
>
> if test "$seccomp" != "no" ; then
> - if test "$cpu" = "i386" || test "$cpu" = "x86_64" &&
> - $pkg_config --atleast-version=2.1.1 libseccomp; then
> + case "$cpu" in
> + i386|x86_64)
> + libseccomp_minver="2.1.1"
> + ;;
> + arm|aarch64)
> + libseccomp_minver="2.2.3"
> + ;;
> + *)
> + libseccomp_minver=""
> + ;;
> + esac
> +
> + if test "$libseccomp_minver" != "" &&
> + $pkg_config --atleast-version=$libseccomp_minver libseccomp ; then
> libs_softmmu="$libs_softmmu `$pkg_config --libs libseccomp`"
> QEMU_CFLAGS="$QEMU_CFLAGS `$pkg_config --cflags libseccomp`"
> - seccomp="yes"
> + seccomp="yes"
> else
> - if test "$seccomp" = "yes"; then
> - feature_not_found "libseccomp" "Install libseccomp devel >= 2.1.1"
> - fi
> - seccomp="no"
> + if test "$seccomp" = "yes" ; then
> + if test "$libseccomp_minver" != "" ; then
> + feature_not_found "libseccomp" \
> + "Install libseccomp devel >= $libseccomp_minver"
> + else
> + feature_not_found "libseccomp" \
> + "libseccomp is not supported for host cpu $cpu"
> + fi
> + fi
> + seccomp="no"
> fi
> fi
> ##########################################
> --
> 2.5.2
>
The patch does look good, but I'll just delay a little bit the pull
request due to more patches incoming. I just want to create a single
batch. Is ok if we just merge it mid or end of next week?
Thanks for the contribution.
Acked-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>
--
Eduardo Otubo
ProfitBricks GmbH
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-02 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 15:59 [Qemu-devel] [PATCH] configure: arm/aarch64: allow enable-seccomp Andrew Jones
2015-10-02 14:02 ` Eduardo Otubo [this message]
2015-10-02 14:23 ` Andrew Jones
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=20151002140212.GA25464@vader \
--to=eduardo.otubo@profitbricks.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).