[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFyyJpCC0EFfPpGYi+6goWbA+LZbrkFcLNW3x8xYHfKvdQ@mail.gmail.com>
Date: Wed, 4 Sep 2013 10:53:47 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] perf changes for v3.12
On Tue, Sep 3, 2013 at 6:29 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> Please pull the latest perf-core-for-linus git tree from:
I don't think this is new at all, but I just tried to do a perf
record/report of "make -j64 test" on git:
It's a big perf.data file (1.6G), but after it has done the
"processing time ordered events" thing it results in:
┌─Warning:───────────────────────────────────┐
│Processed 8672030 events and lost 71 chunks!│
│Check IO/CPU overload! │
│ │
│ │
│Press any key... │
└────────────────────────────────────────────┘
and then it just hangs using 100% CPU time. Pressing any key doesn't
do anything.
It may well still be *doing* something, and maybe it will come back
some day with results. But it sure doesn't show any indication that it
will.
Try this (in a current git source tree: note, by "git" I actually mean
git itself, not some random git repository)::
perf record -g -e cycles:pp make -j64 test >& out
perf report
maybe you can reproduce it.
Linus
Powered by blists - more mailing lists