linux-kernel - Re: [PATCH] simplify update_times (avoid jiffies/jiffies

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: <6e0cfd1d0608020550k7ae2c44dg94afbe56d66b@mail.gmail.com>
Date:	Wed, 2 Aug 2006 14:50:32 +0200
From:	"Martin Schwidefsky" <schwidefsky@...glemail.com>
To:	"Atsushi Nemoto" <anemo@....ocn.ne.jp>
Cc:	johnstul@...ibm.com, akpm@...l.org, zippel@...ux-m68k.org,
	clameter@...r.sgi.com, linux-kernel@...r.kernel.org,
	ralf@...ux-mips.org, ak@....de
Subject: Re: [PATCH] simplify update_times (avoid jiffies/jiffies_64 aliasing problem)

On 8/1/06, Atsushi Nemoto <anemo@....ocn.ne.jp> wrote:
> > I think that this is going into the wrong direction. There are a
> > number of architectures that call do_timer(regs) in a while loop. It
> > would be much nicer if do_timer would get the number of passed ticks
> > as an argument. And the "regs" argument to do_timer is just useless.
>
> But normally do_timer() is called just once, isn't it?  These loops
> are just for lost ticks, which would be rarely happened.  So I think
> tunning for usual case is better.

If you switch of the hz timer in idle you'll get lots of lost ticks.
And if you are
running a virtualized system you can loose you cpu for some ticks as well.
Pass the number of ticks to do_timer.

-- 
blue skies,
  Martin
-
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/