Message ID | 1455296713-7417-1-git-send-email-ferseiti@linux.vnet.ibm.com (mailing list archive) |
---|---|
State | Rejected, archived |
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 4EA8295D5; Fri, 12 Feb 2016 18:05:26 +0100 (CET) Received: from e24smtp01.br.ibm.com (e24smtp01.br.ibm.com [32.104.18.85]) by dpdk.org (Postfix) with ESMTP id CC9B195D4 for <dev@dpdk.org>; Fri, 12 Feb 2016 18:05:24 +0100 (CET) Received: from localhost by e24smtp01.br.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <dev@dpdk.org> from <ferseiti@linux.vnet.ibm.com>; Fri, 12 Feb 2016 15:05:22 -0200 Received: from d24dlp01.br.ibm.com (9.18.248.204) by e24smtp01.br.ibm.com (10.172.0.143) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 12 Feb 2016 15:05:20 -0200 X-IBM-Helo: d24dlp01.br.ibm.com X-IBM-MailFrom: ferseiti@linux.vnet.ibm.com X-IBM-RcptTo: dev@dpdk.org Received: from d24relay03.br.ibm.com (d24relay03.br.ibm.com [9.13.184.25]) by d24dlp01.br.ibm.com (Postfix) with ESMTP id C5E2A352006C for <dev@dpdk.org>; Fri, 12 Feb 2016 12:05:11 -0500 (EST) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.8.31.93]) by d24relay03.br.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u1CH2xv650855990 for <dev@dpdk.org>; Fri, 12 Feb 2016 15:03:00 -0200 Received: from d24av02.br.ibm.com (localhost [127.0.0.1]) by d24av02.br.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id u1CH5Hwk001286 for <dev@dpdk.org>; Fri, 12 Feb 2016 15:05:17 -0200 Received: from localhost.localdomain (oc0745135144.ibm.com.br.ibm.com [9.18.235.71] (may be forged)) by d24av02.br.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id u1CH5H57001277; Fri, 12 Feb 2016 15:05:17 -0200 From: Fernando Seiti Furusato <ferseiti@linux.vnet.ibm.com> To: dev@dpdk.org Date: Fri, 12 Feb 2016 12:05:13 -0500 Message-Id: <1455296713-7417-1-git-send-email-ferseiti@linux.vnet.ibm.com> X-Mailer: git-send-email 2.7.0 X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16021217-1524-0000-0000-000004EE8416 Subject: [dpdk-dev] [PATCH] build: set CFLAGS for ppc64el build X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Commit Message
Fernando Seiti Furusato
Feb. 12, 2016, 5:05 p.m. UTC
Add a proper ifeq statement to set the mcpu as needed for ppc64el, as
the only one originally set is not valid for ppc architectures.
Signed-off-by: Fernando Seiti Furusato <ferseiti@linux.vnet.ibm.com>
---
mk/machine/default/rte.vars.mk | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
Comments
2016-02-12 12:05, Fernando Seiti Furusato: > Add a proper ifeq statement to set the mcpu as needed for ppc64el, as > the only one originally set is not valid for ppc architectures. What is the benefit of using the default machine config, compared to the power8 one? Don't you think the default machine should be renamed core2? [...] > +ifeq (ppc64le,$(shell uname -m)) > + MACHINE_CFLAGS += -mcpu=power8 Why this flag is not set in mk/machine/power8/rte.vars.mk ?
Hello Thomas. Thanks for your quick response. On 02/12/2016 03:37 PM, Thomas Monjalon wrote: > 2016-02-12 12:05, Fernando Seiti Furusato: >> Add a proper ifeq statement to set the mcpu as needed for ppc64el, as >> the only one originally set is not valid for ppc architectures. > > What is the benefit of using the default machine config, compared to > the power8 one? > > Don't you think the default machine should be renamed core2? I think it would be better indeed. Thanks for pointing that out. > > [...] >> +ifeq (ppc64le,$(shell uname -m)) >> + MACHINE_CFLAGS += -mcpu=power8 > > Why this flag is not set in mk/machine/power8/rte.vars.mk ? > This and what observed above would make a better patch. Let me try those. Thanks!
Hi Thomas. On 02/12/2016 05:18 PM, Fernando Seiti Furusato wrote: > Hello Thomas. > Thanks for your quick response. > > On 02/12/2016 03:37 PM, Thomas Monjalon wrote: >> 2016-02-12 12:05, Fernando Seiti Furusato: >>> Add a proper ifeq statement to set the mcpu as needed for ppc64el, as >>> the only one originally set is not valid for ppc architectures. >> >> What is the benefit of using the default machine config, compared to >> the power8 one? >> >> Don't you think the default machine should be renamed core2? > > I think it would be better indeed. Thanks for pointing that out. > >> >> [...] >>> +ifeq (ppc64le,$(shell uname -m)) >>> + MACHINE_CFLAGS += -mcpu=power8 >> >> Why this flag is not set in mk/machine/power8/rte.vars.mk ? >> > > This and what observed above would make a better patch. > Let me try those. I will be just changing the flag within mk/machine/power8/rte.vars.mk so it will be used on ppc64le. I thought since I am not sure how it will affect others, I will not mess with the default file. I had to copy config/defconfig_ppc_64-power8-linuxapp-gcc to config/defconfig_ppc64le-native-linuxapp-gcc, because the build searches for it on ppc64le. Should I include that in the patch? Do you think there is a better approach? Thanks and regards.
2016-02-16 16:04, Fernando Seiti Furusato: > Hi Thomas. > > On 02/12/2016 05:18 PM, Fernando Seiti Furusato wrote: > > Hello Thomas. > > Thanks for your quick response. > > > > On 02/12/2016 03:37 PM, Thomas Monjalon wrote: > >> 2016-02-12 12:05, Fernando Seiti Furusato: > >>> Add a proper ifeq statement to set the mcpu as needed for ppc64el, as > >>> the only one originally set is not valid for ppc architectures. > >> > >> What is the benefit of using the default machine config, compared to > >> the power8 one? > >> > >> Don't you think the default machine should be renamed core2? > > > > I think it would be better indeed. Thanks for pointing that out. > > > >> > >> [...] > >>> +ifeq (ppc64le,$(shell uname -m)) > >>> + MACHINE_CFLAGS += -mcpu=power8 > >> > >> Why this flag is not set in mk/machine/power8/rte.vars.mk ? > >> > > > > This and what observed above would make a better patch. > > Let me try those. > > I will be just changing the flag within mk/machine/power8/rte.vars.mk so > it will be used on ppc64le. Does it mean that only little endian is supported on POWER8? > I thought since I am not sure how it will affect others, I will not mess > with the default file. Yes let's keep it for another patch if someone is concerned. > I had to copy config/defconfig_ppc_64-power8-linuxapp-gcc to > config/defconfig_ppc64le-native-linuxapp-gcc, because the build searches > for it on ppc64le. Should I include that in the patch? > Do you think there is a better approach? Not sure to understand. I think there is something wrong in the commands you use to compile. Are you using "make config T=ppc_64-power8-linuxapp-gcc" ?
On 02/16/2016 04:09 PM, Thomas Monjalon wrote: > 2016-02-16 16:04, Fernando Seiti Furusato: >> Hi Thomas. >> >> On 02/12/2016 05:18 PM, Fernando Seiti Furusato wrote: >>> Hello Thomas. >>> Thanks for your quick response. >>> >>> On 02/12/2016 03:37 PM, Thomas Monjalon wrote: >>>> 2016-02-12 12:05, Fernando Seiti Furusato: >>>>> Add a proper ifeq statement to set the mcpu as needed for ppc64el, as >>>>> the only one originally set is not valid for ppc architectures. >>>> >>>> What is the benefit of using the default machine config, compared to >>>> the power8 one? >>>> >>>> Don't you think the default machine should be renamed core2? >>> >>> I think it would be better indeed. Thanks for pointing that out. >>> >>>> >>>> [...] >>>>> +ifeq (ppc64le,$(shell uname -m)) >>>>> + MACHINE_CFLAGS += -mcpu=power8 >>>> >>>> Why this flag is not set in mk/machine/power8/rte.vars.mk ? >>>> >>> >>> This and what observed above would make a better patch. >>> Let me try those. >> >> I will be just changing the flag within mk/machine/power8/rte.vars.mk so >> it will be used on ppc64le. > > Does it mean that only little endian is supported on POWER8? Not exactly. It is just that I work mainly on LE. It would probably work on big endian too. > >> I thought since I am not sure how it will affect others, I will not mess >> with the default file. > > Yes let's keep it for another patch if someone is concerned. > >> I had to copy config/defconfig_ppc_64-power8-linuxapp-gcc to >> config/defconfig_ppc64le-native-linuxapp-gcc, because the build searches >> for it on ppc64le. Should I include that in the patch? >> Do you think there is a better approach? > > Not sure to understand. > I think there is something wrong in the commands you use to compile. > Are you using "make config T=ppc_64-power8-linuxapp-gcc" ? > Nah, never mind about this one. You are right, I messed it up. I copied the line from what was generated by debian/rules on the ubuntu package. Thanks.
diff --git a/mk/machine/default/rte.vars.mk b/mk/machine/default/rte.vars.mk index 53c6af6..77b4065 100644 --- a/mk/machine/default/rte.vars.mk +++ b/mk/machine/default/rte.vars.mk @@ -55,4 +55,8 @@ # CPU_LDFLAGS = # CPU_ASFLAGS = -MACHINE_CFLAGS += -march=core2 +ifeq (ppc64le,$(shell uname -m)) + MACHINE_CFLAGS += -mcpu=power8 +else + MACHINE_CFLAGS += -march=core2 +endif