From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mellanox.co.il (mail-il-dmz.mellanox.com [193.47.165.129]) by dpdk.org (Postfix) with ESMTP id 88C35A3 for ; Thu, 2 May 2019 03:58:30 +0200 (CEST) Received: from Internal Mail-Server by MTLPINE2 (envelope-from yskoh@mellanox.com) with ESMTPS (AES256-SHA encrypted); 2 May 2019 04:58:25 +0300 Received: from scfae-sc-2.mti.labs.mlnx (scfae-sc-2.mti.labs.mlnx [10.101.0.96]) by labmailer.mlnx (8.13.8/8.13.8) with ESMTP id x421wJeq029254; Thu, 2 May 2019 04:58:23 +0300 From: Yongseok Koh To: jerinj@marvell.com, shahafs@mellanox.com, thomas@monjalon.net Cc: dev@dpdk.org, bruce.richardson@intel.com, pbhagavatula@marvell.com, gavin.hu@arm.com, Honnappa.Nagarahalli@arm.com Date: Wed, 1 May 2019 18:58:06 -0700 Message-Id: <20190502015806.41497-2-yskoh@mellanox.com> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20190502015806.41497-1-yskoh@mellanox.com> References: <20190502015806.41497-1-yskoh@mellanox.com> Subject: [dpdk-dev] [PATCH 2/2] mk: disable armv8 crypto extension for Mellanox BlueField X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 May 2019 01:58:30 -0000 Mellanox BlueField has a variant which doesn't have armv8 crypto extension. If crypto enabled binary runs on such a pltform, rte_eal_init() fails. To have binary compatibility across multiple variants, it is disabled by default and can be enabled for crypto enabled parts. Signed-off-by: Yongseok Koh --- config/defconfig_arm64-bluefield-linuxapp-gcc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/config/defconfig_arm64-bluefield-linuxapp-gcc b/config/defconfig_arm64-bluefield-linuxapp-gcc index b496538819..6da9c2026d 100644 --- a/config/defconfig_arm64-bluefield-linuxapp-gcc +++ b/config/defconfig_arm64-bluefield-linuxapp-gcc @@ -10,6 +10,12 @@ CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72" CONFIG_RTE_MAX_NUMA_NODES=1 CONFIG_RTE_CACHE_LINE_SIZE=64 +# Crypto extension of armv8 +# +# Disabled by default for binary compatibility. +# Can be enabled for crypto-enabled parts. +CONFIG_RTE_ENABLE_ARMV8_CRYPTO=n + # UMA architecture CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n CONFIG_RTE_LIBRTE_VHOST_NUMA=n -- 2.11.0 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id D97D5A0AC5 for ; Thu, 2 May 2019 03:58:33 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 228601DB9; Thu, 2 May 2019 03:58:32 +0200 (CEST) Received: from mellanox.co.il (mail-il-dmz.mellanox.com [193.47.165.129]) by dpdk.org (Postfix) with ESMTP id 88C35A3 for ; Thu, 2 May 2019 03:58:30 +0200 (CEST) Received: from Internal Mail-Server by MTLPINE2 (envelope-from yskoh@mellanox.com) with ESMTPS (AES256-SHA encrypted); 2 May 2019 04:58:25 +0300 Received: from scfae-sc-2.mti.labs.mlnx (scfae-sc-2.mti.labs.mlnx [10.101.0.96]) by labmailer.mlnx (8.13.8/8.13.8) with ESMTP id x421wJeq029254; Thu, 2 May 2019 04:58:23 +0300 From: Yongseok Koh To: jerinj@marvell.com, shahafs@mellanox.com, thomas@monjalon.net Cc: dev@dpdk.org, bruce.richardson@intel.com, pbhagavatula@marvell.com, gavin.hu@arm.com, Honnappa.Nagarahalli@arm.com Date: Wed, 1 May 2019 18:58:06 -0700 Message-Id: <20190502015806.41497-2-yskoh@mellanox.com> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20190502015806.41497-1-yskoh@mellanox.com> References: <20190502015806.41497-1-yskoh@mellanox.com> Subject: [dpdk-dev] [PATCH 2/2] mk: disable armv8 crypto extension for Mellanox BlueField X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Content-Type: text/plain; charset="UTF-8" Message-ID: <20190502015806.tIpDWO_n0hRiMiZm3MgH1tF_-IPf8UoNJSxC7zmu750@z> Mellanox BlueField has a variant which doesn't have armv8 crypto extension. If crypto enabled binary runs on such a pltform, rte_eal_init() fails. To have binary compatibility across multiple variants, it is disabled by default and can be enabled for crypto enabled parts. Signed-off-by: Yongseok Koh --- config/defconfig_arm64-bluefield-linuxapp-gcc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/config/defconfig_arm64-bluefield-linuxapp-gcc b/config/defconfig_arm64-bluefield-linuxapp-gcc index b496538819..6da9c2026d 100644 --- a/config/defconfig_arm64-bluefield-linuxapp-gcc +++ b/config/defconfig_arm64-bluefield-linuxapp-gcc @@ -10,6 +10,12 @@ CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72" CONFIG_RTE_MAX_NUMA_NODES=1 CONFIG_RTE_CACHE_LINE_SIZE=64 +# Crypto extension of armv8 +# +# Disabled by default for binary compatibility. +# Can be enabled for crypto-enabled parts. +CONFIG_RTE_ENABLE_ARMV8_CRYPTO=n + # UMA architecture CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n CONFIG_RTE_LIBRTE_VHOST_NUMA=n -- 2.11.0