linux-kernel - Re: [patch 2.6.26] /dev/hpet

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: <4886E164.2070304@ladisch.de>
Date:	Wed, 23 Jul 2008 09:44:36 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	David Brownell <david-b@...bell.net>
CC:	lkml <linux-kernel@...r.kernel.org>, bob.picco@...com,
	venkatesh.pallipadi@...el.com, Vojtech Pavlik <vojtech@...e.cz>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [patch 2.6.26] /dev/hpet - fixes and cleanup

David Brownell wrote:
>   * Tighten and correct the userspace interface code
>       ...
>       + only open comparators that have an interrupt, and can thus
>         perform "real work"

This prevents userspace applications from doing mmap() on /dev/hpet
even if there is no interrupt.

This seems to be the only part of the userspace interface that is
used in practice.  Because of the availability of POSIX timers, it might
make sense to deprecate the HPET ioctl interface.

> And re that kernel interface:  IMO, worth having a relatively
> generic interface for hardware timers instead of inventing a new
> interface for each new bit of hardware.

AFAIK it was intended to be similar to the RTC callback interface, but
that was before the generic high-precision timer stuff was introduced.


Regards,
Clemens
--
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/