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 719BAA0679 for ; Tue, 30 Apr 2019 19:02:03 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6876558FE; Tue, 30 Apr 2019 19:02:03 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 619E65F0D for ; Tue, 30 Apr 2019 19:02:01 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C61893086235; Tue, 30 Apr 2019 17:02:00 +0000 (UTC) Received: from rh.redhat.com (ovpn-117-211.ams2.redhat.com [10.36.117.211]) by smtp.corp.redhat.com (Postfix) with ESMTP id B25386D0A9; Tue, 30 Apr 2019 17:01:59 +0000 (UTC) From: Kevin Traynor To: Jerin Jacob Cc: Cristian Dumitrescu , dpdk stable Date: Tue, 30 Apr 2019 18:01:05 +0100 Message-Id: <20190430170133.2331-10-ktraynor@redhat.com> In-Reply-To: <20190430170133.2331-1-ktraynor@redhat.com> References: <20190430170133.2331-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.42]); Tue, 30 Apr 2019 17:02:00 +0000 (UTC) Subject: [dpdk-stable] patch 'table: fix arm64 hash function selection' has been queued to LTS release 18.11.2 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 05/07/19. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches can be viewed on a temporary branch at: https://github.com/kevintraynor/dpdk-stable-queue.git Thanks. Kevin Traynor --- >From 4835547e25085c53b0dd5951435dc19445da2a53 Mon Sep 17 00:00:00 2001 From: Jerin Jacob Date: Sat, 6 Apr 2019 13:29:41 +0000 Subject: [PATCH] table: fix arm64 hash function selection [ upstream commit e3eb65cab308508883139b2b79c8348ec0682eec ] Use CRC32 instruction only when it is available to avoid the build issue like below. {standard input}:16: Error: selected processor does not support `crc32cx w3,w3,x0' Fixes: ea7be0a0386e ("lib/librte_table: add hash function headers") Signed-off-by: Jerin Jacob Acked-by: Cristian Dumitrescu --- lib/librte_table/rte_table_hash_func.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/librte_table/rte_table_hash_func.h b/lib/librte_table/rte_table_hash_func.h index 02296eabe..11ea5a90e 100644 --- a/lib/librte_table/rte_table_hash_func.h +++ b/lib/librte_table/rte_table_hash_func.h @@ -41,5 +41,5 @@ rte_crc32_u64(uint64_t crc, uint64_t v) } -#elif defined(RTE_ARCH_ARM64) +#elif defined(RTE_ARCH_ARM64) && defined(RTE_MACHINE_CPUFLAG_CRC32) #include "rte_table_hash_func_arm64.h" #else -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-04-30 17:58:14.295165546 +0100 +++ 0010-table-fix-arm64-hash-function-selection.patch 2019-04-30 17:58:13.765140639 +0100 @@ -1 +1 @@ -From e3eb65cab308508883139b2b79c8348ec0682eec Mon Sep 17 00:00:00 2001 +From 4835547e25085c53b0dd5951435dc19445da2a53 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit e3eb65cab308508883139b2b79c8348ec0682eec ] + @@ -13 +14,0 @@ -Cc: stable@dpdk.org