linux-kernel - Re: [PATCH for 2.6.19] Fix xtime losing ticks

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: <200611161758.56348.ak@suse.de>
Date:	Thu, 16 Nov 2006 17:58:56 +0100
From:	Andi Kleen <ak@...e.de>
To:	Jiri Bohac <jbohac@...e.cz>
Cc:	linux-kernel@...r.kernel.org, vojtech@...e.cz
Subject: Re: [PATCH for 2.6.19] Fix xtime losing ticks

On Thursday 16 November 2006 17:52, Jiri Bohac wrote:
> xtime is not properly incremented when main timer ticks are lost.
> Whatever the number of ticks elapsed is, only one tick worth of time
> is added to xtime. This patch fixes that.

Normally it is supposed to be called as often as there are missing
ticks (e.g. see s390 implementation of noidletick). This is also
true for non no idle tick - the hardware is not supposed to lose
interrupts.

You would need to change at least the existing noidletick implementations
in tree too.

Anyways, i'm sure it could be improved, but in .20 with dyntick
everything will be different anyways. I don't think it makes sense
to change now.

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