[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=V61L6vgFZ_4u20dZvv2=tvi-XJMc2HqOnjMo4@mail.gmail.com>
Date: Tue, 25 Jan 2011 06:27:31 +1000
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Frédéric Weisbecker <fweisbec@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] perf fixes
On Tue, Jan 25, 2011 at 6:17 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> It only happens for me with "g". With "perf record -af sleep 10" it worked.
Actually, it's something subtler than that. It must depend on the
actual data, because now when I tried it again, it worked with 'g'
too. I hadn't saved the old perf.data that caused the lockup (it got
overwritten by the non-g test), and now when I try to re-create it it
doesn't hang on the result.
So it's probably some very specific data pattern that causes it.
(And I don't know if it's a hard hang - it could just be something
_very_ slow. But we're talking half a minute kind of slow).
Linus
--
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