linux-kernel - Re: [RFC] Reentrant clock sources

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:	Wed, 26 Nov 2008 04:07:20 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Magnus Damm <magnus.damm@...il.com>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, lethal@...ux-sh.org,
	johnstul@...ibm.com, mingo@...hat.com
Subject: Re: [RFC] Reentrant clock sources


* Thomas Gleixner <tglx@...utronix.de> wrote:

> > +	cycle_t (*vread)(struct clocksource *cs);
> 
> This is crap. vread can not access the clocksource.

i think 'reentrant' in the sense of creating self-sufficient driver 
entities. vread wont (and shouldnt) call ->vread() recursively - but 
it might want to access fields on the clocksource.

this way more dynamic clocksource drivers could be written. Am i 
missing something?

	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/