[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150511123304.GA28716@gmail.com>
Date: Mon, 11 May 2015 14:33:04 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Will Deacon <will.deacon@....com>
Cc: David Ahern <david.ahern@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Rutland <Mark.Rutland@....com>,
"jolsa@...nel.org" <jolsa@...nel.org>,
"namhyung@...nel.org" <namhyung@...nel.org>,
"acme@...hat.com" <acme@...hat.com>
Subject: Re: arm/arm64 perf build issue with mainline
* Will Deacon <will.deacon@....com> wrote:
> On Mon, May 11, 2015 at 09:21:20AM +0100, Ingo Molnar wrote:
> > * David Ahern <david.ahern@...cle.com> wrote:
> > > On 4/23/15 5:29 AM, Will Deacon wrote:
> > > >Commit 6428c59a97de ("perf tools: Set JOBS based on CPU or processor")
> > > >causes weird behaviour on arm/arm64 platforms because we use the "CPU"
> > > >prefix for things like:
> > > >
> > > >CPU implementer : 0x41
> > > >CPU architecture: 8
> > > >CPU variant : 0x0
> > > >CPU part : 0xd03
> > > >CPU revision : 0
> > > >
> > > >in /proc/cpuinfo. Consequently, a 6 core machine ends up doing:
> > > >
> > > >will@...finement-loaf:~/linux/tools/perf$ make
> > > > BUILD: Doing 'make -j36' parallel build
> > > >
> > > >which is a little overwhelming. Any chance we can predicate the extra
> > > >part of the regex on $(ARCH) being sparc?
> >
> > That regex needs to be fixed or replaced with a more robust 'number of
> > CPUs on the system' discovery method.
>
> That was already proposed here (as part of the fallback from getconf):
>
> https://lkml.kernel.org/r/20150427190356.GD474@krava.redhat.com
>
> but I'm not sure what happened to the patch.
Sending out the latest/best version as a reminder for Arnaldo will
sure help it along.
Acked-by: Ingo Molnar <mingo@...nel.org>
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists