[6/6] mk: disable armv8 crypto extension for Mellanox BlueField
diff mbox series

Message ID 20190412232451.30197-7-yskoh@mellanox.com
State Superseded, archived
Delegated to: Thomas Monjalon
Headers show
  • build: fix build for arm64
Related show


Context Check Description
ci/checkpatch success coding style OK
ci/Intel-compilation success Compilation OK

Commit Message

Yongseok Koh April 12, 2019, 11:24 p.m. UTC
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 <yskoh@mellanox.com>
 config/defconfig_arm64-bluefield-linuxapp-gcc | 6 ++++++
 1 file changed, 6 insertions(+)

diff mbox series

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"
+# Crypto extension of armv8
+# Disabled by default for binary compatibility.
+# Can be enabled for crypto-enabled parts.
 # UMA architecture