linux-kernel - Re: [PATCH] x86: printk_time to use tsc before cpu

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: <1219823233.6462.38.camel@twins>
Date:	Wed, 27 Aug 2008 09:47:13 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: printk_time to use tsc before cpu_clock is ready

On Wed, 2008-08-27 at 09:42 +0200, Ingo Molnar wrote:
> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
> 
> > +static unsigned long long tsc_clock(int cpu)
> > +{
> > +	unsigned long long t;
> > +
> > +	rdtscll(t);
> > +
> > +	return t;
> > +}
> 
> hm, i'm not sure i like the whole direction - this reintroduces 
> printk_clock in essence.
> 
> how about initializing cpu_clock() sooner, so that printk timestamps 
> start ticking as soon as possible?

which will make some archs quite unhappy iirc, see those arm and ia64
bugs I caused the other day.

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