linux-kernel - Re: [GIT PULL] perf fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110125001658.GA17623@elte.hu>
Date:	Tue, 25 Jan 2011 01:16:58 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	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


* Arnaldo Carvalho de Melo <acme@...hat.com> wrote:

> Em Mon, Jan 24, 2011 at 10:25:26PM +0100, Ingo Molnar escreveu:
> > * Arnaldo Carvalho de Melo <acme@...hat.com> wrote:
> > > Was this on a freshly installed machine? Or on a freshly updated one?
> > > 
> > > Probably its the build-id collecting at the end of a session, on the
> > > first run you had a cold cache and it had to figure out which binaries
> > > to cache on ~/.debug, second time it was already cached so it was fast.
> > 
> > Hm, it would be nice to not surprise users with an unlimited-timeout, up to half a 
> > minute 'frozen' app. Can we possibly display a more finegrained progress indicator?
> 
> Definetely, adding this to the todo list.
> 
> In fact perf_session__process_events already has an ui_progress stuff,
> its just that it works only on report/TUI. Need to make it work with
> some /-|/- spinning text progress indicator after a "collecting
> build-ids:" string, something like that.

Yeah, something like that would awesome!

No need for it to be particularly pretty or complex - just _some_ minimal feedback 
to the user gives us most of the bang for the buck already.

( And, of course, the best solution is to make it all run even faster. When it comes
  to debuginfo data structures i can not prevent myself from thinking 'bloat!' ;-)

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/