linux-kernel - Re: printk timestamps jumping back and forth in 2.6.25-rc.

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: <20080229194457.GB21249@elte.hu>
Date:	Fri, 29 Feb 2008 20:44:57 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>
Cc:	paulus@...ba.org, alexey.zaytsev@...il.com, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: printk timestamps jumping back and forth in 2.6.25-rc.


* David Miller <davem@...emloft.net> wrote:

> From: Paul Mackerras <paulus@...ba.org>
> Date: Fri, 29 Feb 2008 22:11:26 +1100
> 
> > On powerpc we use the timebase register, which is synchronized across
> > CPUs, so if this will add unnecessary overhead, we will want to way to
> > turn it off on powerpc (assuming this ends up going upstream).
> 
> Similarly on sparc64, all of our TSCs are fully synchronized so this 
> complexity is completely unnecessary.

i suspect for them the easiest way is to expose time_sync_thresh and let 
them set it to ULONG_MAX - which skips all synchronization overhead and 
complexity.

	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/