linux-kernel - Re: [PATCH 3/3] perf record/report: Process events in order

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] [day] [month] [year] [list]

Date:	Tue, 7 Dec 2010 13:24:16 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
cc:	Ian Munsie <imunsie@....ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 3/3] perf record/report: Process events in order

On Tue, 7 Dec 2010, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 07, 2010 at 11:47:35AM +0100, Thomas Gleixner escreveu:
> > Having time ordered output of -D needs more than fixing the time stamp
> > issue. The dump_printf/dump_trace stuff is scattered all over the
> > place. So that needs more code churn, as you want to output the non
> > synth events when the ordered queue is drained.
> 
> We can fix that, but then it was supposed to be a dump, something as it
> comes from the perf.data file.
> 
> Perhaps we need something new, that does ordered dumps, I think we can
> just move all the dump_fprintf stuff to one place, and have calls for
> those where it is now (unordered) and another one from the ordered
> place, but looking at different debug variables?

I have a patch series ready to consolidate all this. Will send soon.

Thanks,

	tglx
--
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/