linux-kernel - Re: 'global' rq->clock

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]

Date:	Sat, 3 May 2008 21:37:01 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>
Cc:	a.p.zijlstra@...llo.nl, efault@....de, elendil@...net.nl,
	parag.warudkar@...il.com, linux-kernel@...r.kernel.org,
	guichaz@...oo.fr, andi@...stfloor.org
Subject: Re: 'global' rq->clock


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

> From: Ingo Molnar <mingo@...e.hu>
> Date: Sat, 3 May 2008 12:10:16 +0200
> 
> > ( although please note that the growing generalization that goes on
> >   _did_ find a subtle nohz problem on sparc64 early in the merge 
> >   window, so it's not like these changes are totally useless to you. 
> >   )
> 
> Note that this bug theoretically exists on every platform, even x86, 
> and only sparc64 is fixed at the moment by adding the 
> irq_{entry,exit}() guards around all of it's IPI handlers.
> 
> Just a reminder.

yeah, indeed - it's masked on x86 by the suckiness of most clockevents 
hw timers. We dont get unlimited sleep time like sparc64 does :-/

	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/