From: Ingo Molnar <mingo@kernel.org>
To: Laura Abbott <labbott@redhat.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: Intermittent perf build failures
Date: Sun, 16 Oct 2016 09:14:45 +0200 [thread overview]
Message-ID: <20161016071445.GA7103@gmail.com> (raw)
In-Reply-To: <8f82966d-51ac-7c32-24ca-49e2b43fce06@redhat.com>
* Laura Abbott <labbott@redhat.com> wrote:
> On 10/12/2016 03:12 AM, Jiri Olsa wrote:
> >On Tue, Oct 11, 2016 at 02:18:49PM -0700, Laura Abbott wrote:
> >>On 10/11/2016 01:59 PM, Jiri Olsa wrote:
> >>>On Tue, Oct 11, 2016 at 01:43:36PM -0700, Laura Abbott wrote:
> >>>>Hi,
> >>>>
> >>>>While building today's Fedora rawhide kernel, there was a failure
> >>>>building perf with -j4 [1]:
> >
> >ok, the -j 4 is the problem
> >
> >running "make -j 4 install-bin install-traceevent-plugins"
> >
> > BUILD: Doing 'make -j4' parallel build
> > BUILD: Doing 'make -j4' parallel build
> >
> >will run paralel make instances for install-bin and install-traceevent-plugins
> >which will eventually touch same files and crash..
> >
> >the main perf Makefile is actualy detecting number of cpus
> >and runs Makefile.perf with -j X option so there's no need
> >to specify it on top level.. you can always customize it via
> >JOBS=X make variable
> >
> >so if you don't specify the -j X option it will run the
> >'Makefile.perf install-bin install-traceevent-plugins' with
> >-j X set and it should execute sequentialy and fix your problem
> >
>
> Thanks for pointing that out. The build command has been there
> a while and apparently has bit rotted. I've removed the extra
> -j X flags from the command.
It would also be nice to fix the underlying perf build system problem as well: it
should be entirely fine for people to type 'make -j4'.
Thanks,
Ingo
next prev parent reply other threads:[~2016-10-16 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 20:43 Intermittent perf build failures Laura Abbott
2016-10-11 20:59 ` Jiri Olsa
[not found] ` <0babd89f-dd38-89f5-7073-6b74c6692995@redhat.com>
2016-10-12 10:12 ` Jiri Olsa
2016-10-12 18:18 ` Laura Abbott
2016-10-16 7:14 ` Ingo Molnar [this message]
2016-10-16 15:01 ` Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161016071445.GA7103@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.