mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	Jan Kratochvil <jkratoch@redhat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Milian Wolff <milian.wolff@kdab.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Taeung Song <treeze.taeung@gmail.com>,
	Wang Nan <wangnan0@huawei.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/7] perf/core improvements and fixes
Date: Tue, 24 Nov 2015 10:26:18 +0100	[thread overview]
Message-ID: <20151124092618.GA5359@krava.brq.redhat.com> (raw)
In-Reply-To: <20151124084210.GA31160@gmail.com>

On Tue, Nov 24, 2015 at 09:42:10AM +0100, Ingo Molnar wrote:

SNIP

> > 
> > > 
> > > Occasionally it also triggers a build failure:
> > > 
> > >   CC       plugin_kvm.o
> > >   CC       arch/common.o
> > >   CC       util/db-export.o
> > >   LD       plugin_kmem-in.o
> > > fixdep: error opening depfile: ./.plugin_kmem.o.d: No such file or directory
> > > /home/mingo/tip/tools/build/Makefile.build:77: recipe for target 'plugin_kmem.o' 
> > > failed
> > > make[3]: *** [plugin_kmem.o] Error 2
> > > Makefile:189: recipe for target 'plugin_kmem-in.o' failed
> > > make[2]: *** [plugin_kmem-in.o] Error 2
> > > Makefile.perf:424: recipe for target 'install-traceevent-plugins' failed
> > > make[1]: *** [install-traceevent-plugins] Error 2
> > > make[1]: *** Waiting for unfinished jobs....
> > > 
> > > that too seems to be a result of unwanted, over-eager parallelism.
> > 
> > hm, haven't seen that one for long time now ;-) will check
> 
> So maybe that's a side effect, because I do:
> 
>   make clean install
> 
> and maybe 'clean' happens in parallel with 'install'?

the fixdep error indicates that it was invoked after building object
plugin_kmem-in.o, but it could not find its dep file (.plugin_kmem-in.o.d)
which is built within the object build.. so seems like race with clean
or other build of the same object

however ;-)

The 'Makefile' processing itself isn't paralel and will exec
clean and install targets serialized:

---
[root@intel-wildcatpass-07 perf]# make clean install
make -f Makefile.perf --no-print-directory -j88 O=  clean
  CLEAN    libtraceevent
  CLEAN    libapi
  CLEAN    libbpf
  CLEAN    config
  CLEAN    core-objs
  CLEAN    core-progs
  CLEAN    core-gen
  SUBDIR   Documentation
  CLEAN    Documentation
  CLEAN    python
  BUILD:   Doing 'make -j88' parallel build
make -f Makefile.perf --no-print-directory -j88 O=  install

Auto-detecting system features:
...                         dwarf: [ on  ]
...                         glibc: [ on  ]
---

I can't make that failure on 88 cpus server, I assume you can
reproduce this fairly easily?

Could you please share failing build output from:
  $ make V=1 clean install

thanks,
jirka


  reply	other threads:[~2015-11-24  9:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 21:53 Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 1/7] perf callchain: Move initial entry call into get_entries function Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 2/7] perf callchain: Add order support for libunwind DWARF unwinder Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 3/7] perf test: Add callchain order setup for DWARF unwinder test Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 4/7] perf callchain: Add order support for libdw DWARF unwinder Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 5/7] perf tools: Add 'perf config' command Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 6/7] perf config: Add initial man page Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 7/7] perf callchain: Add missing parent_val initialization Arnaldo Carvalho de Melo
2015-11-24  8:10 ` [GIT PULL 0/7] perf/core improvements and fixes Ingo Molnar
2015-11-24  8:28   ` Jiri Olsa
2015-11-24  8:42     ` Ingo Molnar
2015-11-24  9:26       ` Jiri Olsa [this message]
2015-11-24  9:47         ` Jiri Olsa
2015-11-26 11:00           ` Ingo Molnar
2015-11-26 12:47             ` Jiri Olsa
2015-11-26  7:56         ` Ingo Molnar
2015-11-26  8:12           ` Ingo Molnar
2015-11-26  9:09             ` Jiri Olsa
2015-11-24 10:28   ` Jiri Olsa
2015-11-26  8:13   ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2017-04-13 19:35 Arnaldo Carvalho de Melo
2017-04-14 16:07 ` Arnaldo Carvalho de Melo
2017-04-17  8:15   ` Ingo Molnar
2015-06-12  2:15 Arnaldo Carvalho de Melo
2015-06-12  8:09 ` Ingo Molnar
2015-04-10 21:40 Arnaldo Carvalho de Melo
2015-04-11  6:33 ` Ingo Molnar
2014-06-23  7:59 Jiri Olsa
2014-06-25  5:44 ` Ingo Molnar
2014-04-28 11:59 Jiri Olsa
2014-04-29  6:42 ` Ingo Molnar
2013-11-07 15:04 Arnaldo Carvalho de Melo
2013-11-07 15:26 ` Ingo Molnar
2012-06-27 19:20 Arnaldo Carvalho de Melo
2012-06-29 13:12 ` Ingo Molnar
2012-07-02  8:01   ` Dmitry Antipov
2012-03-05 15:55 Arnaldo Carvalho de Melo
2012-03-05 16:02 ` Ingo Molnar

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=20151124092618.GA5359@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=jkratoch@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=milian.wolff@kdab.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=treeze.taeung@gmail.com \
    --cc=wangnan0@huawei.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome