From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 480935F16 for ; Thu, 11 Apr 2019 08:59:24 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 86A8421FE0; Thu, 11 Apr 2019 02:59:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 11 Apr 2019 02:59:23 -0400 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=0GYZ4fPJxWx37eqvhy+zKkjyVEo8Os+sYe1saDO5Kus=; b=V9/Vpuq4AkXU 4o3ednWwSAXwa/aOr3gqIqmuysKbB9zkrm9fX6v1Bh6tVm/vVDcemcGHFGe9rpw3 7pGomijMaN5VSp4ErB93W4BjPGU6KH7o08FIImoS0/IgUKRa9H/z5az/2GnpFBHa 1FEaLjD4IHyKPgEFHzVX0Xac0jNEZFk= 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=fm2; bh=0GYZ4fPJxWx37eqvhy+zKkjyVEo8Os+sYe1saDO5K us=; b=ov4Ddryt6bcGCmShrqKp2UskACE672QeZgWG73mpRFzBdomToChS1er7G E+t93sgLJUhZbTKfLpyy8fdME6whMq5H3WwYipwLRttl/j4LlpOFSjZI7zvnWtE9 c0VAdJVvDxbladpmJ+k1qsxogqpB410M5QX26Pycw+ZrFX7isifSFXtgSAZLrEW8 pTbMRcRT/STyW44itrHLeVtTBhDdYp4zBsr0AuWdT7Pj+uAxZTr8RIUaiEPGEQJJ IQjvSdzUzIZBGkjxrLhbPAg6wbbFjVHb7S6ERR9RQKZYbnwVquuKHAPUvoCv4KcT U5EE5H4jMTqTqmUFp2T+JFwlzRWBw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudekgddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 60FEA10316; Thu, 11 Apr 2019 02:59:22 -0400 (EDT) From: Thomas Monjalon To: Pradeep Satyanarayana Cc: dev@dpdk.org, David Christensen , Vivian Kong , David Wilder Date: Thu, 11 Apr 2019 08:59:21 +0200 Message-ID: <1843731.FgQhzGvkNt@xps> In-Reply-To: References: <20190409190630.31975-1-vivkong@ca.ibm.com> <2584431.R4fyAWvymm@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC 00/12] introduce s390x architecture 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, 11 Apr 2019 06:59:24 -0000 10/04/2019 23:45, Pradeep Satyanarayana: > > > > The IBM Power team is not idle in this area. There's ongoing work to > > > enable DTS on Power systems. > > > > Good to read there is some work in the pipe. > > I can remember the first emails (in 2015) talking about some automated > > tests for compilation and unit tests on IBM Power. > > Thomas, Unfortunately we previously had some churn in the teams that worked > on DPDK > on Power. That had a downstream impact. We (Power) should be in better > shape than we > were in the past. For the last several weeks, we have been regularly > running a sub-set of > DTS with unit tests, sample applications and so on against the master > branch. We are also > periodically running these tests against several of the stable branches as > well. Good. Next step will be to report some test result for each patchset submitted on the mailing-list, so we can monitor the results from patchwork. > > We are still seeing some compilation issues regularly on Power. > > Before going to DTS, I think you should extend your compilation testing, > > and basic feature testing with builtin unit tests. > > We have not observed any compilation issues since we started the CI. The > last issue reported > was during 18.11-rc1 that Mellanox fixed. Hopefully, we should catch any > such regressions > quickly in the future, since we now have a CI that runs periodically. There are some failure when compiling with big endian toolchain. It seems you are not testing big endian. If you don't support big endian, please mention it in the doc. > On a different note, I will reach out to Vivian and the s390 team. Thank you 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 9B80FA0096 for ; Thu, 11 Apr 2019 08:59:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EDD505F19; Thu, 11 Apr 2019 08:59:24 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 480935F16 for ; Thu, 11 Apr 2019 08:59:24 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 86A8421FE0; Thu, 11 Apr 2019 02:59:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 11 Apr 2019 02:59:23 -0400 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=0GYZ4fPJxWx37eqvhy+zKkjyVEo8Os+sYe1saDO5Kus=; b=V9/Vpuq4AkXU 4o3ednWwSAXwa/aOr3gqIqmuysKbB9zkrm9fX6v1Bh6tVm/vVDcemcGHFGe9rpw3 7pGomijMaN5VSp4ErB93W4BjPGU6KH7o08FIImoS0/IgUKRa9H/z5az/2GnpFBHa 1FEaLjD4IHyKPgEFHzVX0Xac0jNEZFk= 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=fm2; bh=0GYZ4fPJxWx37eqvhy+zKkjyVEo8Os+sYe1saDO5K us=; b=ov4Ddryt6bcGCmShrqKp2UskACE672QeZgWG73mpRFzBdomToChS1er7G E+t93sgLJUhZbTKfLpyy8fdME6whMq5H3WwYipwLRttl/j4LlpOFSjZI7zvnWtE9 c0VAdJVvDxbladpmJ+k1qsxogqpB410M5QX26Pycw+ZrFX7isifSFXtgSAZLrEW8 pTbMRcRT/STyW44itrHLeVtTBhDdYp4zBsr0AuWdT7Pj+uAxZTr8RIUaiEPGEQJJ IQjvSdzUzIZBGkjxrLhbPAg6wbbFjVHb7S6ERR9RQKZYbnwVquuKHAPUvoCv4KcT U5EE5H4jMTqTqmUFp2T+JFwlzRWBw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudekgddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 60FEA10316; Thu, 11 Apr 2019 02:59:22 -0400 (EDT) From: Thomas Monjalon To: Pradeep Satyanarayana Cc: dev@dpdk.org, David Christensen , Vivian Kong , David Wilder Date: Thu, 11 Apr 2019 08:59:21 +0200 Message-ID: <1843731.FgQhzGvkNt@xps> In-Reply-To: References: <20190409190630.31975-1-vivkong@ca.ibm.com> <2584431.R4fyAWvymm@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [RFC 00/12] introduce s390x architecture 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" Message-ID: <20190411065921.jiEqXmlik2CPdldEDRGc_kZFkZ7DzDjTnCQoOqhVjzU@z> 10/04/2019 23:45, Pradeep Satyanarayana: > > > > The IBM Power team is not idle in this area. There's ongoing work to > > > enable DTS on Power systems. > > > > Good to read there is some work in the pipe. > > I can remember the first emails (in 2015) talking about some automated > > tests for compilation and unit tests on IBM Power. > > Thomas, Unfortunately we previously had some churn in the teams that worked > on DPDK > on Power. That had a downstream impact. We (Power) should be in better > shape than we > were in the past. For the last several weeks, we have been regularly > running a sub-set of > DTS with unit tests, sample applications and so on against the master > branch. We are also > periodically running these tests against several of the stable branches as > well. Good. Next step will be to report some test result for each patchset submitted on the mailing-list, so we can monitor the results from patchwork. > > We are still seeing some compilation issues regularly on Power. > > Before going to DTS, I think you should extend your compilation testing, > > and basic feature testing with builtin unit tests. > > We have not observed any compilation issues since we started the CI. The > last issue reported > was during 18.11-rc1 that Mellanox fixed. Hopefully, we should catch any > such regressions > quickly in the future, since we now have a CI that runs periodically. There are some failure when compiling with big endian toolchain. It seems you are not testing big endian. If you don't support big endian, please mention it in the doc. > On a different note, I will reach out to Vivian and the s390 team. Thank you