linux-kernel - Re: setting jiffies as the clocksource stops time

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]

Message-ID: <alpine.LFD.0.99999.0801181105390.4642@localhost.localdomain>
Date:	Fri, 18 Jan 2008 11:06:48 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Balaji Rao <balajirrao@...il.com>
cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	Daniel Walker <dwalker@...sta.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: setting jiffies as the clocksource stops time

On Fri, 18 Jan 2008, Balaji Rao wrote:

> On Friday 18 January 2008 04:04:33 am Jan Engelhardt wrote:
> > 
> > On Jan 16 2008 13:20, Daniel Walker wrote:
> > >On Thu, 2008-01-17 at 02:09 +0530, Balaji Rao wrote:
> > >> Hi,
> > >> 
> > >> When i set jiffies as the current_clocksource, date(1) tells me
> > >> that wallclock time has stopped, and soon after that, the system
> > >> becomes unresponsive. This is not seen with CONFIG_NO_HZ disabled.
> > >> 
> > >> I wonder how can jiffies be used as a clocksource.. Its value
> > >> depends on the tick and when we turn off ticks, we would stop
> > >> incrementing jiffies and when we come come out of idle, we update
> > >> the jiffies by reading the current_clocksource which now is
> > >> 'jiffies', and hence jiffies wouldn't get updated. Could this be
> > >> the explanation ?
> > >
> > >Your right, It can't be used as a clocksource with nohz , and the system
> > >will refuse to automatically switch to it ..
> > 
> > I think that manually changing to jiffies by echoing into sysfs
> > should also be prohibited.
> > 
> Yea, right. But why not unregister jiffies as a clocksource itself when we get into NO_HZ ? I think it's much cleaner 
> provided it has no other consequences.

As I said before. I have a patch lined up for the same issue vs. PIT
clocksource and I'm adding that for jiffies as well. It's just not an
urgent issue, which needs to go into .24

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/