From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 0F7F21BE0; Sat, 10 Nov 2018 03:13:35 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7ED1721FCE; Fri, 9 Nov 2018 21:13:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 09 Nov 2018 21:13:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=U/KoclaJ1nQE5HPQySCAEZj/wnNtPTRo8Ugb+emmWjk=; b=U1ApmtJnbXFW u2oWLEyE2FCzjf+jTcp6PDBUq07yyfKHVda67FIyvMpHWW18pLNYonEuE72rm2pe FgR9AYedofAx9IDNHbWzDSRGsiSV7eHH3dON+FzPU/+RjaWQnK/9agaFz/euUS8U nPn7uUvd3HNEQrY5FNKXt+p9luQKzhc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=U/KoclaJ1nQE5HPQySCAEZj/wnNtPTRo8Ugb+emmW jk=; b=TZ75xs0G40Nted5xYpCx7uTaoG0z3uewAPsvXL6D63bp56nIfLCqLFBHc 86k9r9AdyY0ssgFB8ZAq3y/LPSbZnEyWHDOFBFmEeUMDyyDoo9mmzEeXa9agoIiA tRtTRa8yl2lW6FOtEPuTWsSLJP/rYJAsRWNXJTQ3OYtBMhjmWwFjNSea+GfFIehy N6Uzw6tqG81a4SVE/KROXBeGZOmviYmSa4vN3tRATsQLyWZA9H0UtJkEYSMeHrb3 kJjFVPGc8ax5N4HRhBhMOyIi5XoYKtxFeoSw2IXsk8PSWwN66jQmRN872RZhLiPb hCy5CIHyjfGkuvSuIkqFw4vzor5hA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BA354102E0; Fri, 9 Nov 2018 21:13:31 -0500 (EST) From: Thomas Monjalon To: ferruh.yigit@intel.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com Cc: stable@dpdk.org, keith.wiles@intel.com, Yongseok Koh , dev@dpdk.org, Shahaf Shuler , anatoly.burakov@intel.com, justin.parus@microsoft.com, christian.ehrhardt@canonical.com, david.coronel@canonical.com, josh.powers@canonical.com, jay.vosburgh@canonical.com, dan.streetman@canonical.com Date: Sat, 10 Nov 2018 03:13:29 +0100 Message-ID: <15598804.PupyfcORSR@xps> In-Reply-To: <1612642.At0RDolh7h@xps> References: <20181023212318.43082-1-yskoh@mellanox.com> <432F92CE-5714-45DC-B72F-CD8771DAFC89@intel.com> <1612642.At0RDolh7h@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] AVX512 bug on SkyLake 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: , X-List-Received-Date: Sat, 10 Nov 2018 02:13:35 -0000 Below is my conclusion for this bug. An expert of x86 is required to follow-up. Summary: - CPU: Intel Skylake - Linux environment: Ubuntu 18.04 - Compiler: GCC 7 or 8 - Scenario: testpmd crashes when it starts forwarding - Behaviour: AVX2 version of rte_memcpy() fails if optimized for AVX512 - Context: inline rte_memcpy() is called from inline rte_mempool_put_bulk(), called from mlx5_tx_complete() (inline or not) - Analysis: AVX512 optimization changes vmovdqu to vmovdqu8 Latest status can be found in Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=97#c35