public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "John Stultz" <john.stultz@linaro.org>,
	patches@linaro.org, "Arve Hjønnevåg" <arve@android.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Alessandro Zummo" <a.zummo@towertech.it>
Subject: [PATCH 0/3] Posix Alarm Timers patchqueue
Date: Thu, 31 Mar 2011 19:38:36 -0700	[thread overview]
Message-ID: <1301625519-10164-1-git-send-email-john.stultz@linaro.org> (raw)

Now that most of the prerequisite code has been merged,
I wanted to send out the Posix Alarm Timers patchset for
some review in hopes that the details can be worked out
so that it can be merged in 2.6.40 or shortly there after.

Issues I'd like to get feedback on:

1) Does the in-kernel alarm timer interface seem sufficient
for the Android Alarm Timers to adapt to using?

2) For the Posix Alarm Timers, what capabilities should be
required in order to allow an application to set an alarm?

3) For in-kernel alarm timers, should there be some override
or explicit switch in sysfs that allows alarm timers to be
enabled or disabled to allow a user to make sure their system
is not woken up by an alarm timer, if they desire. What should
that switch look like?

Remaining issues/Future work:
1) Currently CLOCK_BOOTTIME is updated from read_persistant_clock(),
however some systems do not support that call, instead using the RTC 
to set the time on resume. I'm working on a hook on resume that allows
the RTC hook to increment the timekeeping sleep time as well.

2) I'd like to try to hook up _ALARM clockids to the timerfd
infrastructure to see if that interface might more closely map
to the Android Alarm Timers interface.

thanks
-john

CC: patches@linaro.org
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>


John Stultz (3):
  timers: Add rb_init_node() to allow for stack allocated rb nodes
  timers: Introduce in-kernel alarm-timer interface
  timers: posix interface for alarm-timers

 include/linux/alarmtimer.h   |   30 ++
 include/linux/posix-timers.h |    2 +
 include/linux/rbtree.h       |    8 +
 include/linux/time.h         |    2 +
 include/linux/timerqueue.h   |    2 +-
 kernel/time/Makefile         |    2 +-
 kernel/time/alarmtimer.c     |  701 ++++++++++++++++++++++++++++++++++++++++++
 7 files changed, 745 insertions(+), 2 deletions(-)
 create mode 100644 include/linux/alarmtimer.h
 create mode 100644 kernel/time/alarmtimer.c

-- 
1.7.3.2.146.gca209


             reply	other threads:[~2011-04-01  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  2:38 John Stultz [this message]
2011-04-01  2:38 ` [PATCH 1/3] timers: Add rb_init_node() to allow for stack allocated rb nodes John Stultz
2011-04-01  2:38 ` [PATCH 2/3] timers: Introduce in-kernel alarm-timer interface John Stultz
2011-04-01  2:38 ` [PATCH 3/3] timers: posix interface for alarm-timers John Stultz

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=1301625519-10164-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=arve@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox