linux-kernel - Re: [PATCH 2/3] perf events: Introduce realtime clock event

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]

Date:	Sun, 20 Feb 2011 13:49:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	David Ahern <daahern@...co.com>, linux-perf-users@...r.kernel.org,
	linux-kernel@...r.kernel.org, acme@...stprotocols.net,
	paulus@...ba.org
Subject: Re: [PATCH 2/3] perf events: Introduce realtime clock event

* Peter Zijlstra <peterz@...radead.org> wrote:

> > Programs that generate time-of-day output are using gettimeofday which is tied 
> > to CLOCK_REALTIME. We want to be able to correlate a perf sample to an entry in 
> > an applications log file.
> 
> Well, you can argue those programs are broken :-), [...]

Then 99% of the world is broken as daylight saving time jumps are part of our lives.

> [...] Imagine the joys of trying to figure out wth happens when DST jumps the 
> clock back an hour and you have an hour of duplicate data.

DST means twice a year the clock jumps back and forth by exactly one hour, on a 
given Saturday night. People debugging logs on Saturday nights and not realizing 
that there's a (always highly publicized) DST switch going on *deserve* to be 
surprised twice a year! :-)

Really, i dont think it's a big issue - and timestamping in *real* time has very 
obvious advantages as its name already suggests.

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/