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:	Fri, 02 May 2008 15:00:01 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	a.p.zijlstra@...llo.nl
Cc:	guichaz@...il.com, efault@....de, elendil@...net.nl,
	parag.warudkar@...il.com, mingo@...e.hu,
	linux-kernel@...r.kernel.org, andi@...stfloor.org
Subject: Re: 'global' rq->clock

From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Date: Fri, 02 May 2008 22:46:05 +0200

> We can toss most of this code on archs like power64, sparc64 and s390x
> which have stable clocks. It just seems wrong to do all this on these
> archs, but don't have much choice on x86.

All of this scheduler runqueue clock business is probably solving
the x86 TSC issue on the wrong level.

I suggest having a char with Andi Kleen about these issues, he's
had some good ideas in the past which were ignored for whatever
reasons...
--
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/