linux-kernel - Re: [patch 1/3] hpet: factor timer allocate from open

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.1007231500180.2616@localhost.localdomain>
Date:	Fri, 23 Jul 2010 15:07:36 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	akpm@...ux-foundation.org
cc:	John Stultz <johnstul@...ibm.com>, maglyx@...il.com,
	clemens@...isch.de, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 1/3] hpet: factor timer allocate from open

On Tue, 20 Jul 2010, akpm@...ux-foundation.org wrote:

> From: Magnus Lynch <maglyx@...il.com>
> 
> The current implementation of the /dev/hpet driver couples opening the
> device with allocating one of the (scarce) timers (aka comparators).  This
> is a limitation in that the main counter may be valuable to applications
> seeking a high-resolution timer who have no use for the interrupt
> generating functionality of the comparators.

And how exactly does this patch provide such functionality ? There is
no interface which allows you to access the counter itself. All what
this patch does is removing the allocation from open() and sprinkle
the allocation all over the place for _ZERO_ benefit.

I really have a hard time to understand why anything would open
/dev/hpet just to do nothing with it.

Thanks,

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