Blame SOURCES/kvm-configure-Allow-enable-seccomp-on-s390x-too.patch

4a2fec
From eb80abd49652e09d10b44da5a75c753e76ef5beb Mon Sep 17 00:00:00 2001
4a2fec
From: Thomas Huth <thuth@redhat.com>
4a2fec
Date: Mon, 2 Oct 2017 07:04:17 +0200
4a2fec
Subject: [PATCH 02/34] configure: Allow --enable-seccomp on s390x, too
4a2fec
4a2fec
RH-Author: Thomas Huth <thuth@redhat.com>
4a2fec
Message-id: <1506927858-5400-2-git-send-email-thuth@redhat.com>
4a2fec
Patchwork-id: 76788
4a2fec
O-Subject: [RHEL-7.5 qemu-kvm-ma PATCH 1/2] configure: Allow --enable-seccomp on s390x, too
4a2fec
Bugzilla: 1491647
4a2fec
RH-Acked-by: Eduardo Otubo <otubo@redhat.com>
4a2fec
RH-Acked-by: Markus Armbruster <armbru@redhat.com>
4a2fec
RH-Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
4a2fec
4a2fec
libseccomp supports s390x since version 2.3.0, and I was able to start
4a2fec
a VM with "-sandbox on" without any obvious problems by using this patch,
4a2fec
so it should be safe to allow --enable-seccomp on s390x nowadays, too.
4a2fec
4a2fec
Signed-off-by: Thomas Huth <thuth@redhat.com>
4a2fec
Message-Id: <1505385363-27717-1-git-send-email-thuth@redhat.com>
4a2fec
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
4a2fec
Acked-by: Eduardo Otubo <otubo@redhat.com>
4a2fec
Acked-by: Halil Pasic <pasic@linux.vnet.ibm.com>
4a2fec
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
4a2fec
(cherry picked from commit 3aa35fcffcf0fe22ac48d4277ed6057ae3e57ce0)
4a2fec
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
4a2fec
---
4a2fec
 configure | 2 +-
4a2fec
 1 file changed, 1 insertion(+), 1 deletion(-)
4a2fec
4a2fec
diff --git a/configure b/configure
4a2fec
index 355c364..5cb65d0 100755
4a2fec
--- a/configure
4a2fec
+++ b/configure
4a2fec
@@ -2050,7 +2050,7 @@ if test "$seccomp" != "no" ; then
4a2fec
     arm|aarch64)
4a2fec
         libseccomp_minver="2.2.3"
4a2fec
         ;;
4a2fec
-    ppc|ppc64)
4a2fec
+    ppc|ppc64|s390x)
4a2fec
         libseccomp_minver="2.3.0"
4a2fec
         ;;
4a2fec
     *)
4a2fec
-- 
4a2fec
1.8.3.1
4a2fec