All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: akpm@linux-foundation.org, maglyx@gmail.com,
	Arnd Bergmann <arnd@arndb.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, 06 Mar 2012 16:04:21 +0100	[thread overview]
Message-ID: <4F562775.2010501@ladisch.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1203061345150.2742@ionos>

Thomas Gleixner wrote:
> 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.

Indeed.  There was another call in hpet_ioctl_common(), but it appears
that one somehow got dropped.

Magnus, is this the patch that you submitted and have tested?


Regards,
Clemens

  reply	other threads:[~2012-03-06 15:02 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 ` [patch 4/4] hpet: factor timer allocate from open Thomas Gleixner
2012-03-06 15:04   ` Clemens Ladisch [this message]
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=4F562775.2010501@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maglyx@gmail.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.