From: Thomas Gleixner <tglx@linutronix.de>
To: akpm@linux-foundation.org
Cc: maglyx@gmail.com, Arnd Bergmann <arnd@arndb.de>,
clemens@ladisch.de, John Stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 4/4] hpet: factor timer allocate from open
Date: Tue, 6 Mar 2012 13:52:41 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1203061345150.2742@ionos> (raw)
In-Reply-To: <20120305230755.35019A02EB@akpm.mtv.corp.google.com>
On Mon, 5 Mar 2012, akpm@linux-foundation.org wrote:
> From: Magnus Lynch <maglyx@gmail.com>
> Subject: hpet: factor timer allocate from open
>
> 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.
>
> This patch alters the open semantics so that when the device is opened, no
> timer is allocated. Operations that depend on a timer being in context
> implicitly attempt allocating a timer, to maintain backward compatibility.
AFAICT, there is only fasync which calls hpet_alloc_timer(). All other
functions are broken by this chage.
> There is also an IOCTL (HPET_ALLOC_TIMER _IO) added so that the
> allocation may be done explicitly. (I prefer the explicit open then
And that IOCTL does what? Return 0 is not really useful functionality.
Thanks,
tglx
next parent reply other threads:[~2012-03-06 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120305230755.35019A02EB@akpm.mtv.corp.google.com>
2012-03-06 12:52 ` Thomas Gleixner [this message]
2012-03-06 15:04 ` [patch 4/4] hpet: factor timer allocate from open Clemens Ladisch
2012-03-06 18:38 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1203061345150.2742@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=clemens@ladisch.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maglyx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox