2018-10-31 18:21:09 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2011-01-11 17:42:13 +00:00
|
|
|
/*
|
|
|
|
* Alarmtimer interface
|
|
|
|
*
|
2021-03-22 21:39:03 +00:00
|
|
|
* This interface provides a timer which is similar to hrtimers,
|
2011-01-11 17:42:13 +00:00
|
|
|
* but triggers a RTC alarm if the box is suspend.
|
|
|
|
*
|
|
|
|
* This interface is influenced by the Android RTC Alarm timer
|
|
|
|
* interface.
|
|
|
|
*
|
2021-03-22 21:39:03 +00:00
|
|
|
* Copyright (C) 2010 IBM Corporation
|
2011-01-11 17:42:13 +00:00
|
|
|
*
|
|
|
|
* Author: John Stultz <john.stultz@linaro.org>
|
|
|
|
*/
|
|
|
|
#include <linux/time.h>
|
|
|
|
#include <linux/hrtimer.h>
|
|
|
|
#include <linux/timerqueue.h>
|
|
|
|
#include <linux/rtc.h>
|
2017-02-02 18:15:33 +00:00
|
|
|
#include <linux/sched/signal.h>
|
2017-02-08 17:51:35 +00:00
|
|
|
#include <linux/sched/debug.h>
|
2011-01-11 17:42:13 +00:00
|
|
|
#include <linux/alarmtimer.h>
|
|
|
|
#include <linux/mutex.h>
|
|
|
|
#include <linux/platform_device.h>
|
|
|
|
#include <linux/posix-timers.h>
|
|
|
|
#include <linux/workqueue.h>
|
|
|
|
#include <linux/freezer.h>
|
2017-06-07 08:42:31 +00:00
|
|
|
#include <linux/compat.h>
|
2017-08-20 22:01:46 +00:00
|
|
|
#include <linux/module.h>
|
2019-11-12 01:27:00 +00:00
|
|
|
#include <linux/time_namespace.h>
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2017-05-30 21:15:41 +00:00
|
|
|
#include "posix-timers.h"
|
|
|
|
|
2016-11-28 22:35:21 +00:00
|
|
|
#define CREATE_TRACE_POINTS
|
|
|
|
#include <trace/events/alarmtimer.h>
|
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
|
|
|
* struct alarm_base - Alarm timer bases
|
|
|
|
* @lock: Lock for syncrhonized access to the base
|
|
|
|
* @timerqueue: Timerqueue head managing the list of events
|
2019-11-12 01:26:56 +00:00
|
|
|
* @get_ktime: Function to read the time correlating to the base
|
2019-11-12 01:26:57 +00:00
|
|
|
* @get_timespec: Function to read the namespace time correlating to the base
|
2011-04-28 19:58:11 +00:00
|
|
|
* @base_clockid: clockid for the base
|
|
|
|
*/
|
2011-01-11 17:42:13 +00:00
|
|
|
static struct alarm_base {
|
|
|
|
spinlock_t lock;
|
|
|
|
struct timerqueue_head timerqueue;
|
2019-11-12 01:26:56 +00:00
|
|
|
ktime_t (*get_ktime)(void);
|
2019-11-12 01:26:57 +00:00
|
|
|
void (*get_timespec)(struct timespec64 *tp);
|
2011-01-11 17:42:13 +00:00
|
|
|
clockid_t base_clockid;
|
|
|
|
} alarm_bases[ALARM_NUMTYPE];
|
|
|
|
|
2017-05-27 10:23:47 +00:00
|
|
|
#if defined(CONFIG_POSIX_TIMERS) || defined(CONFIG_RTC_CLASS)
|
2016-11-28 22:35:21 +00:00
|
|
|
/* freezer information to handle clock_nanosleep triggered wakeups */
|
|
|
|
static enum alarmtimer_type freezer_alarmtype;
|
|
|
|
static ktime_t freezer_expires;
|
2011-06-17 01:27:09 +00:00
|
|
|
static ktime_t freezer_delta;
|
|
|
|
static DEFINE_SPINLOCK(freezer_delta_lock);
|
2017-05-27 10:23:47 +00:00
|
|
|
#endif
|
2011-06-17 01:27:09 +00:00
|
|
|
|
2017-07-05 12:08:35 +00:00
|
|
|
#ifdef CONFIG_RTC_CLASS
|
2011-04-28 19:58:11 +00:00
|
|
|
/* rtc timer and device for setting alarm wakeups at suspend */
|
2012-03-24 11:46:23 +00:00
|
|
|
static struct rtc_timer rtctimer;
|
2011-01-11 17:42:13 +00:00
|
|
|
static struct rtc_device *rtcdev;
|
2011-06-17 01:27:09 +00:00
|
|
|
static DEFINE_SPINLOCK(rtcdev_lock);
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2011-06-17 01:27:09 +00:00
|
|
|
/**
|
|
|
|
* alarmtimer_get_rtcdev - Return selected rtcdevice
|
|
|
|
*
|
|
|
|
* This function returns the rtc device to use for wakealarms.
|
|
|
|
*/
|
2012-04-20 19:31:45 +00:00
|
|
|
struct rtc_device *alarmtimer_get_rtcdev(void)
|
2011-06-17 01:27:09 +00:00
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct rtc_device *ret;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&rtcdev_lock, flags);
|
|
|
|
ret = rtcdev;
|
|
|
|
spin_unlock_irqrestore(&rtcdev_lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
2014-06-13 06:19:42 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarmtimer_get_rtcdev);
|
2011-07-15 01:35:13 +00:00
|
|
|
|
2023-04-02 17:58:49 +00:00
|
|
|
static int alarmtimer_rtc_add_device(struct device *dev)
|
2011-07-15 01:35:13 +00:00
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct rtc_device *rtc = to_rtc_device(dev);
|
2020-01-24 05:58:46 +00:00
|
|
|
struct platform_device *pdev;
|
2020-01-09 15:59:07 +00:00
|
|
|
int ret = 0;
|
2011-07-15 01:35:13 +00:00
|
|
|
|
|
|
|
if (rtcdev)
|
|
|
|
return -EBUSY;
|
|
|
|
|
2021-05-11 01:45:16 +00:00
|
|
|
if (!test_bit(RTC_FEATURE_ALARM, rtc->features))
|
2011-07-15 01:35:13 +00:00
|
|
|
return -1;
|
|
|
|
if (!device_may_wakeup(rtc->dev.parent))
|
|
|
|
return -1;
|
|
|
|
|
2020-01-24 05:58:46 +00:00
|
|
|
pdev = platform_device_register_data(dev, "alarmtimer",
|
|
|
|
PLATFORM_DEVID_AUTO, NULL, 0);
|
2020-01-24 05:58:47 +00:00
|
|
|
if (!IS_ERR(pdev))
|
|
|
|
device_init_wakeup(&pdev->dev, true);
|
2017-07-05 12:08:35 +00:00
|
|
|
|
2011-07-15 01:35:13 +00:00
|
|
|
spin_lock_irqsave(&rtcdev_lock, flags);
|
2020-01-24 05:58:47 +00:00
|
|
|
if (!IS_ERR(pdev) && !rtcdev) {
|
2017-08-20 22:01:46 +00:00
|
|
|
if (!try_module_get(rtc->owner)) {
|
2020-01-09 15:59:07 +00:00
|
|
|
ret = -1;
|
|
|
|
goto unlock;
|
2017-08-20 22:01:46 +00:00
|
|
|
}
|
|
|
|
|
2011-07-15 01:35:13 +00:00
|
|
|
rtcdev = rtc;
|
|
|
|
/* hold a reference so it doesn't go away */
|
|
|
|
get_device(dev);
|
2020-01-24 05:58:46 +00:00
|
|
|
pdev = NULL;
|
|
|
|
} else {
|
|
|
|
ret = -1;
|
2011-07-15 01:35:13 +00:00
|
|
|
}
|
2020-01-09 15:59:07 +00:00
|
|
|
unlock:
|
2011-07-15 01:35:13 +00:00
|
|
|
spin_unlock_irqrestore(&rtcdev_lock, flags);
|
2017-07-05 12:08:35 +00:00
|
|
|
|
2020-01-24 05:58:46 +00:00
|
|
|
platform_device_unregister(pdev);
|
2017-07-05 12:08:35 +00:00
|
|
|
|
2020-01-09 15:59:07 +00:00
|
|
|
return ret;
|
2011-07-15 01:35:13 +00:00
|
|
|
}
|
|
|
|
|
2012-03-24 11:46:23 +00:00
|
|
|
static inline void alarmtimer_rtc_timer_init(void)
|
|
|
|
{
|
|
|
|
rtc_timer_init(&rtctimer, NULL, NULL);
|
|
|
|
}
|
|
|
|
|
2011-07-15 01:35:13 +00:00
|
|
|
static struct class_interface alarmtimer_rtc_interface = {
|
|
|
|
.add_dev = &alarmtimer_rtc_add_device,
|
|
|
|
};
|
|
|
|
|
2011-09-14 08:54:29 +00:00
|
|
|
static int alarmtimer_rtc_interface_setup(void)
|
2011-07-15 01:35:13 +00:00
|
|
|
{
|
|
|
|
alarmtimer_rtc_interface.class = rtc_class;
|
2011-09-14 08:54:29 +00:00
|
|
|
return class_interface_register(&alarmtimer_rtc_interface);
|
|
|
|
}
|
|
|
|
static void alarmtimer_rtc_interface_remove(void)
|
|
|
|
{
|
|
|
|
class_interface_unregister(&alarmtimer_rtc_interface);
|
2011-07-15 01:35:13 +00:00
|
|
|
}
|
2011-06-17 01:47:37 +00:00
|
|
|
#else
|
2011-09-14 08:54:29 +00:00
|
|
|
static inline int alarmtimer_rtc_interface_setup(void) { return 0; }
|
|
|
|
static inline void alarmtimer_rtc_interface_remove(void) { }
|
2012-03-24 11:46:23 +00:00
|
|
|
static inline void alarmtimer_rtc_timer_init(void) { }
|
2011-06-17 01:27:09 +00:00
|
|
|
#endif
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2011-01-11 17:42:13 +00:00
|
|
|
* alarmtimer_enqueue - Adds an alarm timer to an alarm_base timerqueue
|
|
|
|
* @base: pointer to the base where the timer is being run
|
|
|
|
* @alarm: pointer to alarm being enqueued.
|
|
|
|
*
|
2012-09-13 23:12:16 +00:00
|
|
|
* Adds alarm to a alarm_base timerqueue
|
2011-01-11 17:42:13 +00:00
|
|
|
*
|
|
|
|
* Must hold base->lock when calling.
|
|
|
|
*/
|
|
|
|
static void alarmtimer_enqueue(struct alarm_base *base, struct alarm *alarm)
|
|
|
|
{
|
2012-09-13 23:12:16 +00:00
|
|
|
if (alarm->state & ALARMTIMER_STATE_ENQUEUED)
|
|
|
|
timerqueue_del(&base->timerqueue, &alarm->node);
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
timerqueue_add(&base->timerqueue, &alarm->node);
|
2011-08-10 19:30:21 +00:00
|
|
|
alarm->state |= ALARMTIMER_STATE_ENQUEUED;
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2012-09-13 23:25:22 +00:00
|
|
|
* alarmtimer_dequeue - Removes an alarm timer from an alarm_base timerqueue
|
2011-01-11 17:42:13 +00:00
|
|
|
* @base: pointer to the base where the timer is running
|
|
|
|
* @alarm: pointer to alarm being removed
|
|
|
|
*
|
2012-09-13 23:12:16 +00:00
|
|
|
* Removes alarm to a alarm_base timerqueue
|
2011-01-11 17:42:13 +00:00
|
|
|
*
|
|
|
|
* Must hold base->lock when calling.
|
|
|
|
*/
|
2012-09-13 23:25:22 +00:00
|
|
|
static void alarmtimer_dequeue(struct alarm_base *base, struct alarm *alarm)
|
2011-01-11 17:42:13 +00:00
|
|
|
{
|
2011-08-10 19:30:21 +00:00
|
|
|
if (!(alarm->state & ALARMTIMER_STATE_ENQUEUED))
|
|
|
|
return;
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
timerqueue_del(&base->timerqueue, &alarm->node);
|
2011-08-10 19:30:21 +00:00
|
|
|
alarm->state &= ~ALARMTIMER_STATE_ENQUEUED;
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
|
|
|
|
2011-04-28 20:29:18 +00:00
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2011-04-28 20:29:18 +00:00
|
|
|
* alarmtimer_fired - Handles alarm hrtimer being fired.
|
|
|
|
* @timer: pointer to hrtimer being run
|
2011-01-11 17:42:13 +00:00
|
|
|
*
|
2011-04-28 19:58:11 +00:00
|
|
|
* When a alarm timer fires, this runs through the timerqueue to
|
|
|
|
* see which alarms expired, and runs those. If there are more alarm
|
|
|
|
* timers queued for the future, we set the hrtimer to fire when
|
2020-08-07 03:32:48 +00:00
|
|
|
* the next future alarm timer expires.
|
2011-01-11 17:42:13 +00:00
|
|
|
*/
|
2011-04-28 20:29:18 +00:00
|
|
|
static enum hrtimer_restart alarmtimer_fired(struct hrtimer *timer)
|
2011-01-11 17:42:13 +00:00
|
|
|
{
|
2012-09-13 23:12:16 +00:00
|
|
|
struct alarm *alarm = container_of(timer, struct alarm, timer);
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
2011-01-11 17:42:13 +00:00
|
|
|
unsigned long flags;
|
2011-04-28 20:29:18 +00:00
|
|
|
int ret = HRTIMER_NORESTART;
|
2011-08-10 18:08:07 +00:00
|
|
|
int restart = ALARMTIMER_NORESTART;
|
2011-01-11 17:42:13 +00:00
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
2012-09-13 23:25:22 +00:00
|
|
|
alarmtimer_dequeue(base, alarm);
|
2012-09-13 23:12:16 +00:00
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
2011-08-10 18:08:07 +00:00
|
|
|
|
2012-09-13 23:12:16 +00:00
|
|
|
if (alarm->function)
|
2019-11-12 01:26:56 +00:00
|
|
|
restart = alarm->function(alarm, base->get_ktime());
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2012-09-13 23:12:16 +00:00
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
if (restart != ALARMTIMER_NORESTART) {
|
|
|
|
hrtimer_set_expires(&alarm->timer, alarm->node.expires);
|
|
|
|
alarmtimer_enqueue(base, alarm);
|
2011-04-28 20:29:18 +00:00
|
|
|
ret = HRTIMER_RESTART;
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
|
|
|
|
2019-11-12 01:26:56 +00:00
|
|
|
trace_alarmtimer_fired(alarm, base->get_ktime());
|
2011-04-28 20:29:18 +00:00
|
|
|
return ret;
|
2011-01-11 17:42:13 +00:00
|
|
|
|
|
|
|
}
|
|
|
|
|
2013-05-15 21:38:11 +00:00
|
|
|
ktime_t alarm_expires_remaining(const struct alarm *alarm)
|
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
2019-11-12 01:26:56 +00:00
|
|
|
return ktime_sub(alarm->node.expires, base->get_ktime());
|
2013-05-15 21:38:11 +00:00
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_expires_remaining);
|
2013-05-15 21:38:11 +00:00
|
|
|
|
2011-04-29 22:03:10 +00:00
|
|
|
#ifdef CONFIG_RTC_CLASS
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2011-01-11 17:42:13 +00:00
|
|
|
* alarmtimer_suspend - Suspend time callback
|
|
|
|
* @dev: unused
|
|
|
|
*
|
|
|
|
* When we are going into suspend, we look through the bases
|
|
|
|
* to see which is the soonest timer to expire. We then
|
|
|
|
* set an rtc timer to fire that far into the future, which
|
|
|
|
* will wake us from suspend.
|
|
|
|
*/
|
|
|
|
static int alarmtimer_suspend(struct device *dev)
|
|
|
|
{
|
2016-11-28 22:35:21 +00:00
|
|
|
ktime_t min, now, expires;
|
|
|
|
int i, ret, type;
|
2011-06-17 01:27:09 +00:00
|
|
|
struct rtc_device *rtc;
|
2016-11-28 22:35:21 +00:00
|
|
|
unsigned long flags;
|
|
|
|
struct rtc_time tm;
|
2011-01-11 17:42:13 +00:00
|
|
|
|
|
|
|
spin_lock_irqsave(&freezer_delta_lock, flags);
|
|
|
|
min = freezer_delta;
|
2016-11-28 22:35:21 +00:00
|
|
|
expires = freezer_expires;
|
|
|
|
type = freezer_alarmtype;
|
2016-12-25 11:30:41 +00:00
|
|
|
freezer_delta = 0;
|
2011-01-11 17:42:13 +00:00
|
|
|
spin_unlock_irqrestore(&freezer_delta_lock, flags);
|
|
|
|
|
2011-07-15 01:35:13 +00:00
|
|
|
rtc = alarmtimer_get_rtcdev();
|
2011-01-11 17:42:13 +00:00
|
|
|
/* If we have no rtcdev, just return */
|
2011-06-17 01:27:09 +00:00
|
|
|
if (!rtc)
|
2011-01-11 17:42:13 +00:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Find the soonest timer to expire*/
|
|
|
|
for (i = 0; i < ALARM_NUMTYPE; i++) {
|
|
|
|
struct alarm_base *base = &alarm_bases[i];
|
|
|
|
struct timerqueue_node *next;
|
|
|
|
ktime_t delta;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
next = timerqueue_getnext(&base->timerqueue);
|
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
|
|
|
if (!next)
|
|
|
|
continue;
|
2019-11-12 01:26:56 +00:00
|
|
|
delta = ktime_sub(next->expires, base->get_ktime());
|
2016-12-25 10:38:40 +00:00
|
|
|
if (!min || (delta < min)) {
|
2016-11-28 22:35:21 +00:00
|
|
|
expires = next->expires;
|
2011-01-11 17:42:13 +00:00
|
|
|
min = delta;
|
2016-11-28 22:35:21 +00:00
|
|
|
type = i;
|
|
|
|
}
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
2016-12-25 10:38:40 +00:00
|
|
|
if (min == 0)
|
2011-01-11 17:42:13 +00:00
|
|
|
return 0;
|
|
|
|
|
2012-08-09 07:37:27 +00:00
|
|
|
if (ktime_to_ns(min) < 2 * NSEC_PER_SEC) {
|
2020-01-24 05:58:47 +00:00
|
|
|
pm_wakeup_event(dev, 2 * MSEC_PER_SEC);
|
2012-08-09 07:37:27 +00:00
|
|
|
return -EBUSY;
|
|
|
|
}
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2016-11-28 22:35:21 +00:00
|
|
|
trace_alarmtimer_suspend(expires, type);
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
/* Setup an rtc timer to fire that far in the future */
|
2011-06-17 01:27:09 +00:00
|
|
|
rtc_timer_cancel(rtc, &rtctimer);
|
|
|
|
rtc_read_time(rtc, &tm);
|
2011-01-11 17:42:13 +00:00
|
|
|
now = rtc_tm_to_ktime(tm);
|
alarmtimer: Use maximum alarm time for suspend
Some userspace applications use timerfd_create() to request wakeups after
a long period of time. For example, a backup application may request a
wakeup once per week. This is perfectly fine as long as the system does
not try to suspend. However, if the system tries to suspend and the
system's RTC does not support the required alarm timeout, the suspend
operation will fail with an error such as
rtc_cmos 00:01: Alarms can be up to one day in the future
PM: dpm_run_callback(): platform_pm_suspend+0x0/0x4a returns -22
alarmtimer alarmtimer.4.auto: platform_pm_suspend+0x0/0x4a returned -22 after 117 usecs
PM: Device alarmtimer.4.auto failed to suspend: error -22
This results in a refusal to suspend the system, causing substantial
battery drain on affected systems.
To fix the problem, use the maximum alarm time offset as reported by RTC
drivers to set the maximum alarm time. While this may result in early
wakeups from suspend, it is still much better than not suspending at all.
Standardize system behavior if the requested alarm timeout is larger than
the alarm timeout supported by the rtc chip. Currently, in this situation,
the RTC driver will do one of the following:
- It may return an error.
- It may limit the alarm timeout to the maximum supported by the rtc chip.
- It may mask the timeout by the maximum alarm timeout supported by the RTC
chip (i.e. a requested timeout of 1 day + 1 minute may result in a 1
minute timeout).
With this in place, if the RTC driver reports the maximum alarm timeout
supported by the RTC chip, the system will always limit the alarm timeout
to the maximum supported by the RTC chip.
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Link: https://lore.kernel.org/r/20230915152238.1144706-3-linux@roeck-us.net
2023-09-15 15:22:38 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If the RTC alarm timer only supports a limited time offset, set the
|
|
|
|
* alarm time to the maximum supported value.
|
|
|
|
* The system may wake up earlier (possibly much earlier) than expected
|
|
|
|
* when the alarmtimer runs. This is the best the kernel can do if
|
|
|
|
* the alarmtimer exceeds the time that the rtc device can be programmed
|
|
|
|
* for.
|
|
|
|
*/
|
|
|
|
min = rtc_bound_alarmtime(rtc, min);
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
now = ktime_add(now, min);
|
|
|
|
|
2012-08-09 07:37:27 +00:00
|
|
|
/* Set alarm, if in the past reject suspend briefly to handle */
|
2016-12-25 11:30:41 +00:00
|
|
|
ret = rtc_timer_start(rtc, &rtctimer, now, 0);
|
2012-08-09 07:37:27 +00:00
|
|
|
if (ret < 0)
|
2020-01-24 05:58:47 +00:00
|
|
|
pm_wakeup_event(dev, MSEC_PER_SEC);
|
2012-08-09 07:37:27 +00:00
|
|
|
return ret;
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
2015-11-17 12:08:07 +00:00
|
|
|
|
|
|
|
static int alarmtimer_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
struct rtc_device *rtc;
|
|
|
|
|
|
|
|
rtc = alarmtimer_get_rtcdev();
|
|
|
|
if (rtc)
|
|
|
|
rtc_timer_cancel(rtc, &rtctimer);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-04-29 22:03:10 +00:00
|
|
|
#else
|
|
|
|
static int alarmtimer_suspend(struct device *dev)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
2015-11-17 12:08:07 +00:00
|
|
|
|
|
|
|
static int alarmtimer_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
2011-04-29 22:03:10 +00:00
|
|
|
#endif
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2018-03-26 13:29:57 +00:00
|
|
|
static void
|
|
|
|
__alarm_init(struct alarm *alarm, enum alarmtimer_type type,
|
|
|
|
enum alarmtimer_restart (*function)(struct alarm *, ktime_t))
|
|
|
|
{
|
|
|
|
timerqueue_init(&alarm->node);
|
|
|
|
alarm->timer.function = alarmtimer_fired;
|
|
|
|
alarm->function = function;
|
|
|
|
alarm->type = type;
|
|
|
|
alarm->state = ALARMTIMER_STATE_INACTIVE;
|
|
|
|
}
|
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2011-01-11 17:42:13 +00:00
|
|
|
* alarm_init - Initialize an alarm structure
|
|
|
|
* @alarm: ptr to alarm to be initialized
|
|
|
|
* @type: the type of the alarm
|
|
|
|
* @function: callback that is run when the alarm fires
|
|
|
|
*/
|
|
|
|
void alarm_init(struct alarm *alarm, enum alarmtimer_type type,
|
2011-08-10 17:37:59 +00:00
|
|
|
enum alarmtimer_restart (*function)(struct alarm *, ktime_t))
|
2011-01-11 17:42:13 +00:00
|
|
|
{
|
2012-09-13 23:12:16 +00:00
|
|
|
hrtimer_init(&alarm->timer, alarm_bases[type].base_clockid,
|
2018-03-26 13:29:57 +00:00
|
|
|
HRTIMER_MODE_ABS);
|
|
|
|
__alarm_init(alarm, type, function);
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_init);
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2013-05-15 21:38:11 +00:00
|
|
|
* alarm_start - Sets an absolute alarm to fire
|
2011-01-11 17:42:13 +00:00
|
|
|
* @alarm: ptr to alarm to set
|
|
|
|
* @start: time to run the alarm
|
|
|
|
*/
|
2015-04-14 21:09:18 +00:00
|
|
|
void alarm_start(struct alarm *alarm, ktime_t start)
|
2011-01-11 17:42:13 +00:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
alarm->node.expires = start;
|
|
|
|
alarmtimer_enqueue(base, alarm);
|
2015-04-14 21:09:18 +00:00
|
|
|
hrtimer_start(&alarm->timer, alarm->node.expires, HRTIMER_MODE_ABS);
|
2011-01-11 17:42:13 +00:00
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
2016-11-28 22:35:21 +00:00
|
|
|
|
2019-11-12 01:26:56 +00:00
|
|
|
trace_alarmtimer_start(alarm, base->get_ktime());
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_start);
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2013-05-15 21:38:11 +00:00
|
|
|
/**
|
|
|
|
* alarm_start_relative - Sets a relative alarm to fire
|
|
|
|
* @alarm: ptr to alarm to set
|
|
|
|
* @start: time relative to now to run the alarm
|
|
|
|
*/
|
2015-04-14 21:09:18 +00:00
|
|
|
void alarm_start_relative(struct alarm *alarm, ktime_t start)
|
2013-05-15 21:38:11 +00:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
|
2019-11-12 01:26:56 +00:00
|
|
|
start = ktime_add_safe(start, base->get_ktime());
|
2015-04-14 21:09:18 +00:00
|
|
|
alarm_start(alarm, start);
|
2013-05-15 21:38:11 +00:00
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_start_relative);
|
2013-05-15 21:38:11 +00:00
|
|
|
|
|
|
|
void alarm_restart(struct alarm *alarm)
|
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
hrtimer_set_expires(&alarm->timer, alarm->node.expires);
|
|
|
|
hrtimer_restart(&alarm->timer);
|
|
|
|
alarmtimer_enqueue(base, alarm);
|
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_restart);
|
2013-05-15 21:38:11 +00:00
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
2011-08-10 19:41:36 +00:00
|
|
|
* alarm_try_to_cancel - Tries to cancel an alarm timer
|
2011-01-11 17:42:13 +00:00
|
|
|
* @alarm: ptr to alarm to be canceled
|
2011-08-10 19:41:36 +00:00
|
|
|
*
|
|
|
|
* Returns 1 if the timer was canceled, 0 if it was not running,
|
|
|
|
* and -1 if the callback was running
|
2011-01-11 17:42:13 +00:00
|
|
|
*/
|
2011-08-10 19:41:36 +00:00
|
|
|
int alarm_try_to_cancel(struct alarm *alarm)
|
2011-01-11 17:42:13 +00:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
unsigned long flags;
|
2012-09-13 23:12:16 +00:00
|
|
|
int ret;
|
2011-08-10 19:41:36 +00:00
|
|
|
|
2012-09-13 23:12:16 +00:00
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
ret = hrtimer_try_to_cancel(&alarm->timer);
|
|
|
|
if (ret >= 0)
|
2012-09-13 23:25:22 +00:00
|
|
|
alarmtimer_dequeue(base, alarm);
|
2011-01-11 17:42:13 +00:00
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
2016-11-28 22:35:21 +00:00
|
|
|
|
2019-11-12 01:26:56 +00:00
|
|
|
trace_alarmtimer_cancel(alarm, base->get_ktime());
|
2011-08-10 19:41:36 +00:00
|
|
|
return ret;
|
2011-01-11 17:42:13 +00:00
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_try_to_cancel);
|
2011-01-11 17:42:13 +00:00
|
|
|
|
|
|
|
|
2011-08-10 19:41:36 +00:00
|
|
|
/**
|
|
|
|
* alarm_cancel - Spins trying to cancel an alarm timer until it is done
|
|
|
|
* @alarm: ptr to alarm to be canceled
|
|
|
|
*
|
|
|
|
* Returns 1 if the timer was canceled, 0 if it was not active.
|
|
|
|
*/
|
|
|
|
int alarm_cancel(struct alarm *alarm)
|
|
|
|
{
|
|
|
|
for (;;) {
|
|
|
|
int ret = alarm_try_to_cancel(alarm);
|
|
|
|
if (ret >= 0)
|
|
|
|
return ret;
|
2019-07-30 22:33:49 +00:00
|
|
|
hrtimer_cancel_wait_running(&alarm->timer);
|
2011-08-10 19:41:36 +00:00
|
|
|
}
|
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_cancel);
|
2011-08-10 19:41:36 +00:00
|
|
|
|
2011-08-10 18:31:03 +00:00
|
|
|
|
|
|
|
u64 alarm_forward(struct alarm *alarm, ktime_t now, ktime_t interval)
|
|
|
|
{
|
|
|
|
u64 overrun = 1;
|
|
|
|
ktime_t delta;
|
|
|
|
|
|
|
|
delta = ktime_sub(now, alarm->node.expires);
|
|
|
|
|
2016-12-25 10:38:40 +00:00
|
|
|
if (delta < 0)
|
2011-08-10 18:31:03 +00:00
|
|
|
return 0;
|
|
|
|
|
2016-12-25 10:38:40 +00:00
|
|
|
if (unlikely(delta >= interval)) {
|
2011-08-10 18:31:03 +00:00
|
|
|
s64 incr = ktime_to_ns(interval);
|
|
|
|
|
|
|
|
overrun = ktime_divns(delta, incr);
|
|
|
|
|
|
|
|
alarm->node.expires = ktime_add_ns(alarm->node.expires,
|
|
|
|
incr*overrun);
|
|
|
|
|
2016-12-25 10:38:40 +00:00
|
|
|
if (alarm->node.expires > now)
|
2011-08-10 18:31:03 +00:00
|
|
|
return overrun;
|
|
|
|
/*
|
|
|
|
* This (and the ktime_add() below) is the
|
|
|
|
* correction for exact:
|
|
|
|
*/
|
|
|
|
overrun++;
|
|
|
|
}
|
|
|
|
|
2017-05-30 21:15:34 +00:00
|
|
|
alarm->node.expires = ktime_add_safe(alarm->node.expires, interval);
|
2011-08-10 18:31:03 +00:00
|
|
|
return overrun;
|
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_forward);
|
2011-08-10 18:31:03 +00:00
|
|
|
|
alarmtimer: Prevent starvation by small intervals and SIG_IGN
syzbot reported a RCU stall which is caused by setting up an alarmtimer
with a very small interval and ignoring the signal. The reproducer arms the
alarm timer with a relative expiry of 8ns and an interval of 9ns. Not a
problem per se, but that's an issue when the signal is ignored because then
the timer is immediately rearmed because there is no way to delay that
rearming to the signal delivery path. See posix_timer_fn() and commit
58229a189942 ("posix-timers: Prevent softirq starvation by small intervals
and SIG_IGN") for details.
The reproducer does not set SIG_IGN explicitely, but it sets up the timers
signal with SIGCONT. That has the same effect as explicitely setting
SIG_IGN for a signal as SIGCONT is ignored if there is no handler set and
the task is not ptraced.
The log clearly shows that:
[pid 5102] --- SIGCONT {si_signo=SIGCONT, si_code=SI_TIMER, si_timerid=0, si_overrun=316014, si_int=0, si_ptr=NULL} ---
It works because the tasks are traced and therefore the signal is queued so
the tracer can see it, which delays the restart of the timer to the signal
delivery path. But then the tracer is killed:
[pid 5087] kill(-5102, SIGKILL <unfinished ...>
...
./strace-static-x86_64: Process 5107 detached
and after it's gone the stall can be observed:
syzkaller login: [ 79.439102][ C0] hrtimer: interrupt took 68471 ns
[ 184.460538][ C1] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
...
[ 184.658237][ C1] rcu: Stack dump where RCU GP kthread last ran:
[ 184.664574][ C1] Sending NMI from CPU 1 to CPUs 0:
[ 184.669821][ C0] NMI backtrace for cpu 0
[ 184.669831][ C0] CPU: 0 PID: 5108 Comm: syz-executor192 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
...
[ 184.670036][ C0] Call Trace:
[ 184.670041][ C0] <IRQ>
[ 184.670045][ C0] alarmtimer_fired+0x327/0x670
posix_timer_fn() prevents that by checking whether the interval for
timers which have the signal ignored is smaller than a jiffie and
artifically delay it by shifting the next expiry out by a jiffie. That's
accurate vs. the overrun accounting, but slightly inaccurate
vs. timer_gettimer(2).
The comment in that function says what needs to be done and there was a fix
available for the regular userspace induced SIG_IGN mechanism, but that did
not work due to the implicit ignore for SIGCONT and similar signals. This
needs to be worked on, but for now the only available workaround is to do
exactly what posix_timer_fn() does:
Increase the interval of self-rearming timers, which have their signal
ignored, to at least a jiffie.
Interestingly this has been fixed before via commit ff86bf0c65f1
("alarmtimer: Rate limit periodic intervals") already, but that fix got
lost in a later rework.
Reported-by: syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com
Fixes: f2c45807d399 ("alarmtimer: Switch over to generic set/get/rearm routine")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/87k00q1no2.ffs@tglx
2023-02-09 22:25:49 +00:00
|
|
|
static u64 __alarm_forward_now(struct alarm *alarm, ktime_t interval, bool throttle)
|
2013-05-15 21:38:11 +00:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
alarmtimer: Prevent starvation by small intervals and SIG_IGN
syzbot reported a RCU stall which is caused by setting up an alarmtimer
with a very small interval and ignoring the signal. The reproducer arms the
alarm timer with a relative expiry of 8ns and an interval of 9ns. Not a
problem per se, but that's an issue when the signal is ignored because then
the timer is immediately rearmed because there is no way to delay that
rearming to the signal delivery path. See posix_timer_fn() and commit
58229a189942 ("posix-timers: Prevent softirq starvation by small intervals
and SIG_IGN") for details.
The reproducer does not set SIG_IGN explicitely, but it sets up the timers
signal with SIGCONT. That has the same effect as explicitely setting
SIG_IGN for a signal as SIGCONT is ignored if there is no handler set and
the task is not ptraced.
The log clearly shows that:
[pid 5102] --- SIGCONT {si_signo=SIGCONT, si_code=SI_TIMER, si_timerid=0, si_overrun=316014, si_int=0, si_ptr=NULL} ---
It works because the tasks are traced and therefore the signal is queued so
the tracer can see it, which delays the restart of the timer to the signal
delivery path. But then the tracer is killed:
[pid 5087] kill(-5102, SIGKILL <unfinished ...>
...
./strace-static-x86_64: Process 5107 detached
and after it's gone the stall can be observed:
syzkaller login: [ 79.439102][ C0] hrtimer: interrupt took 68471 ns
[ 184.460538][ C1] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
...
[ 184.658237][ C1] rcu: Stack dump where RCU GP kthread last ran:
[ 184.664574][ C1] Sending NMI from CPU 1 to CPUs 0:
[ 184.669821][ C0] NMI backtrace for cpu 0
[ 184.669831][ C0] CPU: 0 PID: 5108 Comm: syz-executor192 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
...
[ 184.670036][ C0] Call Trace:
[ 184.670041][ C0] <IRQ>
[ 184.670045][ C0] alarmtimer_fired+0x327/0x670
posix_timer_fn() prevents that by checking whether the interval for
timers which have the signal ignored is smaller than a jiffie and
artifically delay it by shifting the next expiry out by a jiffie. That's
accurate vs. the overrun accounting, but slightly inaccurate
vs. timer_gettimer(2).
The comment in that function says what needs to be done and there was a fix
available for the regular userspace induced SIG_IGN mechanism, but that did
not work due to the implicit ignore for SIGCONT and similar signals. This
needs to be worked on, but for now the only available workaround is to do
exactly what posix_timer_fn() does:
Increase the interval of self-rearming timers, which have their signal
ignored, to at least a jiffie.
Interestingly this has been fixed before via commit ff86bf0c65f1
("alarmtimer: Rate limit periodic intervals") already, but that fix got
lost in a later rework.
Reported-by: syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com
Fixes: f2c45807d399 ("alarmtimer: Switch over to generic set/get/rearm routine")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/87k00q1no2.ffs@tglx
2023-02-09 22:25:49 +00:00
|
|
|
ktime_t now = base->get_ktime();
|
|
|
|
|
|
|
|
if (IS_ENABLED(CONFIG_HIGH_RES_TIMERS) && throttle) {
|
|
|
|
/*
|
|
|
|
* Same issue as with posix_timer_fn(). Timers which are
|
|
|
|
* periodic but the signal is ignored can starve the system
|
|
|
|
* with a very small interval. The real fix which was
|
|
|
|
* promised in the context of posix_timer_fn() never
|
|
|
|
* materialized, but someone should really work on it.
|
|
|
|
*
|
|
|
|
* To prevent DOS fake @now to be 1 jiffie out which keeps
|
|
|
|
* the overrun accounting correct but creates an
|
|
|
|
* inconsistency vs. timer_gettime(2).
|
|
|
|
*/
|
|
|
|
ktime_t kj = NSEC_PER_SEC / HZ;
|
|
|
|
|
|
|
|
if (interval < kj)
|
|
|
|
now = ktime_add(now, kj);
|
|
|
|
}
|
|
|
|
|
|
|
|
return alarm_forward(alarm, now, interval);
|
|
|
|
}
|
2013-05-15 21:38:11 +00:00
|
|
|
|
alarmtimer: Prevent starvation by small intervals and SIG_IGN
syzbot reported a RCU stall which is caused by setting up an alarmtimer
with a very small interval and ignoring the signal. The reproducer arms the
alarm timer with a relative expiry of 8ns and an interval of 9ns. Not a
problem per se, but that's an issue when the signal is ignored because then
the timer is immediately rearmed because there is no way to delay that
rearming to the signal delivery path. See posix_timer_fn() and commit
58229a189942 ("posix-timers: Prevent softirq starvation by small intervals
and SIG_IGN") for details.
The reproducer does not set SIG_IGN explicitely, but it sets up the timers
signal with SIGCONT. That has the same effect as explicitely setting
SIG_IGN for a signal as SIGCONT is ignored if there is no handler set and
the task is not ptraced.
The log clearly shows that:
[pid 5102] --- SIGCONT {si_signo=SIGCONT, si_code=SI_TIMER, si_timerid=0, si_overrun=316014, si_int=0, si_ptr=NULL} ---
It works because the tasks are traced and therefore the signal is queued so
the tracer can see it, which delays the restart of the timer to the signal
delivery path. But then the tracer is killed:
[pid 5087] kill(-5102, SIGKILL <unfinished ...>
...
./strace-static-x86_64: Process 5107 detached
and after it's gone the stall can be observed:
syzkaller login: [ 79.439102][ C0] hrtimer: interrupt took 68471 ns
[ 184.460538][ C1] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
...
[ 184.658237][ C1] rcu: Stack dump where RCU GP kthread last ran:
[ 184.664574][ C1] Sending NMI from CPU 1 to CPUs 0:
[ 184.669821][ C0] NMI backtrace for cpu 0
[ 184.669831][ C0] CPU: 0 PID: 5108 Comm: syz-executor192 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
...
[ 184.670036][ C0] Call Trace:
[ 184.670041][ C0] <IRQ>
[ 184.670045][ C0] alarmtimer_fired+0x327/0x670
posix_timer_fn() prevents that by checking whether the interval for
timers which have the signal ignored is smaller than a jiffie and
artifically delay it by shifting the next expiry out by a jiffie. That's
accurate vs. the overrun accounting, but slightly inaccurate
vs. timer_gettimer(2).
The comment in that function says what needs to be done and there was a fix
available for the regular userspace induced SIG_IGN mechanism, but that did
not work due to the implicit ignore for SIGCONT and similar signals. This
needs to be worked on, but for now the only available workaround is to do
exactly what posix_timer_fn() does:
Increase the interval of self-rearming timers, which have their signal
ignored, to at least a jiffie.
Interestingly this has been fixed before via commit ff86bf0c65f1
("alarmtimer: Rate limit periodic intervals") already, but that fix got
lost in a later rework.
Reported-by: syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com
Fixes: f2c45807d399 ("alarmtimer: Switch over to generic set/get/rearm routine")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/87k00q1no2.ffs@tglx
2023-02-09 22:25:49 +00:00
|
|
|
u64 alarm_forward_now(struct alarm *alarm, ktime_t interval)
|
|
|
|
{
|
|
|
|
return __alarm_forward_now(alarm, interval, false);
|
2013-05-15 21:38:11 +00:00
|
|
|
}
|
2013-06-04 07:32:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_forward_now);
|
2011-08-10 18:31:03 +00:00
|
|
|
|
2017-05-26 09:03:11 +00:00
|
|
|
#ifdef CONFIG_POSIX_TIMERS
|
|
|
|
|
|
|
|
static void alarmtimer_freezerset(ktime_t absexp, enum alarmtimer_type type)
|
|
|
|
{
|
|
|
|
struct alarm_base *base;
|
|
|
|
unsigned long flags;
|
|
|
|
ktime_t delta;
|
|
|
|
|
|
|
|
switch(type) {
|
|
|
|
case ALARM_REALTIME:
|
|
|
|
base = &alarm_bases[ALARM_REALTIME];
|
|
|
|
type = ALARM_REALTIME_FREEZER;
|
|
|
|
break;
|
|
|
|
case ALARM_BOOTTIME:
|
|
|
|
base = &alarm_bases[ALARM_BOOTTIME];
|
|
|
|
type = ALARM_BOOTTIME_FREEZER;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
WARN_ONCE(1, "Invalid alarm type: %d\n", type);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2019-11-12 01:26:56 +00:00
|
|
|
delta = ktime_sub(absexp, base->get_ktime());
|
2017-05-26 09:03:11 +00:00
|
|
|
|
|
|
|
spin_lock_irqsave(&freezer_delta_lock, flags);
|
|
|
|
if (!freezer_delta || (delta < freezer_delta)) {
|
|
|
|
freezer_delta = delta;
|
|
|
|
freezer_expires = absexp;
|
|
|
|
freezer_alarmtype = type;
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&freezer_delta_lock, flags);
|
|
|
|
}
|
2011-08-10 18:31:03 +00:00
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
* clock2alarm - helper that converts from clockid to alarmtypes
|
|
|
|
* @clockid: clockid.
|
|
|
|
*/
|
|
|
|
static enum alarmtimer_type clock2alarm(clockid_t clockid)
|
|
|
|
{
|
|
|
|
if (clockid == CLOCK_REALTIME_ALARM)
|
|
|
|
return ALARM_REALTIME;
|
|
|
|
if (clockid == CLOCK_BOOTTIME_ALARM)
|
|
|
|
return ALARM_BOOTTIME;
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
* alarm_handle_timer - Callback for posix timers
|
|
|
|
* @alarm: alarm that fired
|
2021-02-02 01:34:57 +00:00
|
|
|
* @now: time at the timer expiration
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
*
|
|
|
|
* Posix timer callback for expired alarm timers.
|
2021-02-02 01:34:57 +00:00
|
|
|
*
|
|
|
|
* Return: whether the timer is to be restarted
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
*/
|
2011-08-10 17:37:59 +00:00
|
|
|
static enum alarmtimer_restart alarm_handle_timer(struct alarm *alarm,
|
|
|
|
ktime_t now)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
{
|
|
|
|
struct k_itimer *ptr = container_of(alarm, struct k_itimer,
|
2017-05-30 21:15:59 +00:00
|
|
|
it.alarm.alarmtimer);
|
2014-09-10 01:31:05 +00:00
|
|
|
enum alarmtimer_restart result = ALARMTIMER_NORESTART;
|
2017-05-30 21:15:59 +00:00
|
|
|
unsigned long flags;
|
|
|
|
int si_private = 0;
|
2014-09-10 01:31:05 +00:00
|
|
|
|
|
|
|
spin_lock_irqsave(&ptr->it_lock, flags);
|
2011-08-10 17:37:59 +00:00
|
|
|
|
2017-05-30 21:15:59 +00:00
|
|
|
ptr->it_active = 0;
|
|
|
|
if (ptr->it_interval)
|
|
|
|
si_private = ++ptr->it_requeue_pending;
|
|
|
|
|
|
|
|
if (posix_timer_event(ptr, si_private) && ptr->it_interval) {
|
|
|
|
/*
|
|
|
|
* Handle ignored signals and rearm the timer. This will go
|
alarmtimer: Prevent starvation by small intervals and SIG_IGN
syzbot reported a RCU stall which is caused by setting up an alarmtimer
with a very small interval and ignoring the signal. The reproducer arms the
alarm timer with a relative expiry of 8ns and an interval of 9ns. Not a
problem per se, but that's an issue when the signal is ignored because then
the timer is immediately rearmed because there is no way to delay that
rearming to the signal delivery path. See posix_timer_fn() and commit
58229a189942 ("posix-timers: Prevent softirq starvation by small intervals
and SIG_IGN") for details.
The reproducer does not set SIG_IGN explicitely, but it sets up the timers
signal with SIGCONT. That has the same effect as explicitely setting
SIG_IGN for a signal as SIGCONT is ignored if there is no handler set and
the task is not ptraced.
The log clearly shows that:
[pid 5102] --- SIGCONT {si_signo=SIGCONT, si_code=SI_TIMER, si_timerid=0, si_overrun=316014, si_int=0, si_ptr=NULL} ---
It works because the tasks are traced and therefore the signal is queued so
the tracer can see it, which delays the restart of the timer to the signal
delivery path. But then the tracer is killed:
[pid 5087] kill(-5102, SIGKILL <unfinished ...>
...
./strace-static-x86_64: Process 5107 detached
and after it's gone the stall can be observed:
syzkaller login: [ 79.439102][ C0] hrtimer: interrupt took 68471 ns
[ 184.460538][ C1] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
...
[ 184.658237][ C1] rcu: Stack dump where RCU GP kthread last ran:
[ 184.664574][ C1] Sending NMI from CPU 1 to CPUs 0:
[ 184.669821][ C0] NMI backtrace for cpu 0
[ 184.669831][ C0] CPU: 0 PID: 5108 Comm: syz-executor192 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
...
[ 184.670036][ C0] Call Trace:
[ 184.670041][ C0] <IRQ>
[ 184.670045][ C0] alarmtimer_fired+0x327/0x670
posix_timer_fn() prevents that by checking whether the interval for
timers which have the signal ignored is smaller than a jiffie and
artifically delay it by shifting the next expiry out by a jiffie. That's
accurate vs. the overrun accounting, but slightly inaccurate
vs. timer_gettimer(2).
The comment in that function says what needs to be done and there was a fix
available for the regular userspace induced SIG_IGN mechanism, but that did
not work due to the implicit ignore for SIGCONT and similar signals. This
needs to be worked on, but for now the only available workaround is to do
exactly what posix_timer_fn() does:
Increase the interval of self-rearming timers, which have their signal
ignored, to at least a jiffie.
Interestingly this has been fixed before via commit ff86bf0c65f1
("alarmtimer: Rate limit periodic intervals") already, but that fix got
lost in a later rework.
Reported-by: syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com
Fixes: f2c45807d399 ("alarmtimer: Switch over to generic set/get/rearm routine")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/87k00q1no2.ffs@tglx
2023-02-09 22:25:49 +00:00
|
|
|
* away once we handle ignored signals proper. Ensure that
|
|
|
|
* small intervals cannot starve the system.
|
2017-05-30 21:15:59 +00:00
|
|
|
*/
|
alarmtimer: Prevent starvation by small intervals and SIG_IGN
syzbot reported a RCU stall which is caused by setting up an alarmtimer
with a very small interval and ignoring the signal. The reproducer arms the
alarm timer with a relative expiry of 8ns and an interval of 9ns. Not a
problem per se, but that's an issue when the signal is ignored because then
the timer is immediately rearmed because there is no way to delay that
rearming to the signal delivery path. See posix_timer_fn() and commit
58229a189942 ("posix-timers: Prevent softirq starvation by small intervals
and SIG_IGN") for details.
The reproducer does not set SIG_IGN explicitely, but it sets up the timers
signal with SIGCONT. That has the same effect as explicitely setting
SIG_IGN for a signal as SIGCONT is ignored if there is no handler set and
the task is not ptraced.
The log clearly shows that:
[pid 5102] --- SIGCONT {si_signo=SIGCONT, si_code=SI_TIMER, si_timerid=0, si_overrun=316014, si_int=0, si_ptr=NULL} ---
It works because the tasks are traced and therefore the signal is queued so
the tracer can see it, which delays the restart of the timer to the signal
delivery path. But then the tracer is killed:
[pid 5087] kill(-5102, SIGKILL <unfinished ...>
...
./strace-static-x86_64: Process 5107 detached
and after it's gone the stall can be observed:
syzkaller login: [ 79.439102][ C0] hrtimer: interrupt took 68471 ns
[ 184.460538][ C1] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
...
[ 184.658237][ C1] rcu: Stack dump where RCU GP kthread last ran:
[ 184.664574][ C1] Sending NMI from CPU 1 to CPUs 0:
[ 184.669821][ C0] NMI backtrace for cpu 0
[ 184.669831][ C0] CPU: 0 PID: 5108 Comm: syz-executor192 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
...
[ 184.670036][ C0] Call Trace:
[ 184.670041][ C0] <IRQ>
[ 184.670045][ C0] alarmtimer_fired+0x327/0x670
posix_timer_fn() prevents that by checking whether the interval for
timers which have the signal ignored is smaller than a jiffie and
artifically delay it by shifting the next expiry out by a jiffie. That's
accurate vs. the overrun accounting, but slightly inaccurate
vs. timer_gettimer(2).
The comment in that function says what needs to be done and there was a fix
available for the regular userspace induced SIG_IGN mechanism, but that did
not work due to the implicit ignore for SIGCONT and similar signals. This
needs to be worked on, but for now the only available workaround is to do
exactly what posix_timer_fn() does:
Increase the interval of self-rearming timers, which have their signal
ignored, to at least a jiffie.
Interestingly this has been fixed before via commit ff86bf0c65f1
("alarmtimer: Rate limit periodic intervals") already, but that fix got
lost in a later rework.
Reported-by: syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com
Fixes: f2c45807d399 ("alarmtimer: Switch over to generic set/get/rearm routine")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/87k00q1no2.ffs@tglx
2023-02-09 22:25:49 +00:00
|
|
|
ptr->it_overrun += __alarm_forward_now(alarm, ptr->it_interval, true);
|
2017-05-30 21:15:59 +00:00
|
|
|
++ptr->it_requeue_pending;
|
|
|
|
ptr->it_active = 1;
|
2014-09-10 01:31:05 +00:00
|
|
|
result = ALARMTIMER_RESTART;
|
2011-08-10 18:08:07 +00:00
|
|
|
}
|
2014-09-10 01:31:05 +00:00
|
|
|
spin_unlock_irqrestore(&ptr->it_lock, flags);
|
|
|
|
|
|
|
|
return result;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
}
|
|
|
|
|
2017-05-30 21:15:54 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_rearm - Posix timer callback for rearming timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
*/
|
|
|
|
static void alarm_timer_rearm(struct k_itimer *timr)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
|
|
|
|
timr->it_overrun += alarm_forward_now(alarm, timr->it_interval);
|
|
|
|
alarm_start(alarm, alarm->node.expires);
|
|
|
|
}
|
|
|
|
|
2017-05-30 21:15:55 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_forward - Posix timer callback for forwarding timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
* @now: Current time to forward the timer against
|
|
|
|
*/
|
2018-06-26 13:21:31 +00:00
|
|
|
static s64 alarm_timer_forward(struct k_itimer *timr, ktime_t now)
|
2017-05-30 21:15:55 +00:00
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
|
2018-06-26 13:21:31 +00:00
|
|
|
return alarm_forward(alarm, timr->it_interval, now);
|
2017-05-30 21:15:55 +00:00
|
|
|
}
|
|
|
|
|
2017-05-30 21:15:56 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_remaining - Posix timer callback to retrieve remaining time
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
* @now: Current time to calculate against
|
|
|
|
*/
|
|
|
|
static ktime_t alarm_timer_remaining(struct k_itimer *timr, ktime_t now)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
|
2019-04-08 04:15:42 +00:00
|
|
|
return ktime_sub(alarm->node.expires, now);
|
2017-05-30 21:15:56 +00:00
|
|
|
}
|
|
|
|
|
2017-05-30 21:15:57 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_try_to_cancel - Posix timer callback to cancel a timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
*/
|
|
|
|
static int alarm_timer_try_to_cancel(struct k_itimer *timr)
|
|
|
|
{
|
|
|
|
return alarm_try_to_cancel(&timr->it.alarm.alarmtimer);
|
|
|
|
}
|
|
|
|
|
2019-08-02 05:35:59 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_wait_running - Posix timer callback to wait for a timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
*
|
|
|
|
* Called from the core code when timer cancel detected that the callback
|
|
|
|
* is running. @timr is unlocked and rcu read lock is held to prevent it
|
|
|
|
* from being freed.
|
|
|
|
*/
|
|
|
|
static void alarm_timer_wait_running(struct k_itimer *timr)
|
|
|
|
{
|
|
|
|
hrtimer_cancel_wait_running(&timr->it.alarm.alarmtimer.timer);
|
|
|
|
}
|
|
|
|
|
2017-05-30 21:15:58 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_arm - Posix timer callback to arm a timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
* @expires: The new expiry time
|
|
|
|
* @absolute: Expiry value is absolute time
|
|
|
|
* @sigev_none: Posix timer does not deliver signals
|
|
|
|
*/
|
|
|
|
static void alarm_timer_arm(struct k_itimer *timr, ktime_t expires,
|
|
|
|
bool absolute, bool sigev_none)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
|
|
|
|
if (!absolute)
|
2019-11-12 01:26:56 +00:00
|
|
|
expires = ktime_add_safe(expires, base->get_ktime());
|
2017-05-30 21:15:58 +00:00
|
|
|
if (sigev_none)
|
|
|
|
alarm->node.expires = expires;
|
|
|
|
else
|
|
|
|
alarm_start(&timr->it.alarm.alarmtimer, expires);
|
|
|
|
}
|
|
|
|
|
2011-04-28 19:58:11 +00:00
|
|
|
/**
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
* alarm_clock_getres - posix getres interface
|
|
|
|
* @which_clock: clockid
|
|
|
|
* @tp: timespec to fill
|
|
|
|
*
|
|
|
|
* Returns the granularity of underlying alarm base clock
|
|
|
|
*/
|
2017-03-26 19:04:15 +00:00
|
|
|
static int alarm_clock_getres(const clockid_t which_clock, struct timespec64 *tp)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
{
|
2011-06-17 01:47:37 +00:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
2013-10-14 21:33:16 +00:00
|
|
|
return -EINVAL;
|
2011-06-17 01:47:37 +00:00
|
|
|
|
2015-04-14 21:08:32 +00:00
|
|
|
tp->tv_sec = 0;
|
|
|
|
tp->tv_nsec = hrtimer_resolution;
|
|
|
|
return 0;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2019-11-12 01:26:55 +00:00
|
|
|
* alarm_clock_get_timespec - posix clock_get_timespec interface
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
* @which_clock: clockid
|
|
|
|
* @tp: timespec to fill.
|
|
|
|
*
|
2019-11-12 01:26:58 +00:00
|
|
|
* Provides the underlying alarm base time in a tasks time namespace.
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
*/
|
2019-11-12 01:26:55 +00:00
|
|
|
static int alarm_clock_get_timespec(clockid_t which_clock, struct timespec64 *tp)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[clock2alarm(which_clock)];
|
|
|
|
|
2011-06-17 01:47:37 +00:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
2013-10-14 21:33:16 +00:00
|
|
|
return -EINVAL;
|
2011-06-17 01:47:37 +00:00
|
|
|
|
2019-11-12 01:26:57 +00:00
|
|
|
base->get_timespec(tp);
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2019-11-12 01:26:58 +00:00
|
|
|
/**
|
|
|
|
* alarm_clock_get_ktime - posix clock_get_ktime interface
|
|
|
|
* @which_clock: clockid
|
|
|
|
*
|
|
|
|
* Provides the underlying alarm base time in the root namespace.
|
|
|
|
*/
|
|
|
|
static ktime_t alarm_clock_get_ktime(clockid_t which_clock)
|
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[clock2alarm(which_clock)];
|
|
|
|
|
|
|
|
if (!alarmtimer_get_rtcdev())
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
return base->get_ktime();
|
|
|
|
}
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_create - posix timer_create interface
|
|
|
|
* @new_timer: k_itimer pointer to manage
|
|
|
|
*
|
|
|
|
* Initializes the k_itimer structure.
|
|
|
|
*/
|
|
|
|
static int alarm_timer_create(struct k_itimer *new_timer)
|
|
|
|
{
|
|
|
|
enum alarmtimer_type type;
|
|
|
|
|
2011-06-17 01:47:37 +00:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
2019-09-03 17:18:02 +00:00
|
|
|
return -EOPNOTSUPP;
|
2011-06-17 01:47:37 +00:00
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
if (!capable(CAP_WAKE_ALARM))
|
|
|
|
return -EPERM;
|
|
|
|
|
|
|
|
type = clock2alarm(new_timer->it_clock);
|
2011-08-10 19:09:24 +00:00
|
|
|
alarm_init(&new_timer->it.alarm.alarmtimer, type, alarm_handle_timer);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarmtimer_nsleep_wakeup - Wakeup function for alarm_timer_nsleep
|
|
|
|
* @alarm: ptr to alarm that fired
|
2021-02-02 01:34:57 +00:00
|
|
|
* @now: time at the timer expiration
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
*
|
|
|
|
* Wakes up the task that set the alarmtimer
|
2021-02-02 01:34:57 +00:00
|
|
|
*
|
|
|
|
* Return: ALARMTIMER_NORESTART
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
*/
|
2011-08-10 17:37:59 +00:00
|
|
|
static enum alarmtimer_restart alarmtimer_nsleep_wakeup(struct alarm *alarm,
|
|
|
|
ktime_t now)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
{
|
2023-06-09 18:20:59 +00:00
|
|
|
struct task_struct *task = alarm->data;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
|
|
|
alarm->data = NULL;
|
|
|
|
if (task)
|
|
|
|
wake_up_process(task);
|
2011-08-10 17:37:59 +00:00
|
|
|
return ALARMTIMER_NORESTART;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarmtimer_do_nsleep - Internal alarmtimer nsleep implementation
|
|
|
|
* @alarm: ptr to alarmtimer
|
|
|
|
* @absexp: absolute expiration time
|
2021-02-02 01:34:57 +00:00
|
|
|
* @type: alarm type (BOOTTIME/REALTIME).
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
*
|
|
|
|
* Sets the alarm timer and sleeps until it is fired or interrupted.
|
|
|
|
*/
|
2017-06-07 08:42:27 +00:00
|
|
|
static int alarmtimer_do_nsleep(struct alarm *alarm, ktime_t absexp,
|
|
|
|
enum alarmtimer_type type)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
{
|
2017-06-07 08:42:31 +00:00
|
|
|
struct restart_block *restart;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
alarm->data = (void *)current;
|
|
|
|
do {
|
|
|
|
set_current_state(TASK_INTERRUPTIBLE);
|
2011-08-10 19:09:24 +00:00
|
|
|
alarm_start(alarm, absexp);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
if (likely(alarm->data))
|
|
|
|
schedule();
|
|
|
|
|
|
|
|
alarm_cancel(alarm);
|
|
|
|
} while (alarm->data && !signal_pending(current));
|
|
|
|
|
|
|
|
__set_current_state(TASK_RUNNING);
|
|
|
|
|
2018-03-26 13:29:57 +00:00
|
|
|
destroy_hrtimer_on_stack(&alarm->timer);
|
|
|
|
|
2017-06-07 08:42:27 +00:00
|
|
|
if (!alarm->data)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
return 0;
|
|
|
|
|
2017-06-07 08:42:27 +00:00
|
|
|
if (freezing(current))
|
|
|
|
alarmtimer_freezerset(absexp, type);
|
2017-06-07 08:42:31 +00:00
|
|
|
restart = ¤t->restart_block;
|
|
|
|
if (restart->nanosleep.type != TT_NONE) {
|
2017-06-24 18:45:06 +00:00
|
|
|
struct timespec64 rmt;
|
2017-06-07 08:42:27 +00:00
|
|
|
ktime_t rem;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2019-11-12 01:26:56 +00:00
|
|
|
rem = ktime_sub(absexp, alarm_bases[type].get_ktime());
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2017-06-07 08:42:27 +00:00
|
|
|
if (rem <= 0)
|
|
|
|
return 0;
|
2017-06-24 18:45:06 +00:00
|
|
|
rmt = ktime_to_timespec64(rem);
|
2017-06-07 08:42:27 +00:00
|
|
|
|
2017-06-07 08:42:32 +00:00
|
|
|
return nanosleep_copyout(restart, &rmt);
|
2017-06-07 08:42:27 +00:00
|
|
|
}
|
|
|
|
return -ERESTART_RESTARTBLOCK;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
}
|
|
|
|
|
2018-03-26 13:29:57 +00:00
|
|
|
static void
|
|
|
|
alarm_init_on_stack(struct alarm *alarm, enum alarmtimer_type type,
|
|
|
|
enum alarmtimer_restart (*function)(struct alarm *, ktime_t))
|
|
|
|
{
|
|
|
|
hrtimer_init_on_stack(&alarm->timer, alarm_bases[type].base_clockid,
|
|
|
|
HRTIMER_MODE_ABS);
|
|
|
|
__alarm_init(alarm, type, function);
|
|
|
|
}
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
/**
|
|
|
|
* alarm_timer_nsleep_restart - restartblock alarmtimer nsleep
|
|
|
|
* @restart: ptr to restart block
|
|
|
|
*
|
|
|
|
* Handles restarted clock_nanosleep calls
|
|
|
|
*/
|
|
|
|
static long __sched alarm_timer_nsleep_restart(struct restart_block *restart)
|
|
|
|
{
|
2011-05-20 11:05:15 +00:00
|
|
|
enum alarmtimer_type type = restart->nanosleep.clockid;
|
2017-06-07 08:42:27 +00:00
|
|
|
ktime_t exp = restart->nanosleep.expires;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
struct alarm alarm;
|
|
|
|
|
2018-03-26 13:29:57 +00:00
|
|
|
alarm_init_on_stack(&alarm, type, alarmtimer_nsleep_wakeup);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2017-06-07 08:42:27 +00:00
|
|
|
return alarmtimer_do_nsleep(&alarm, exp, type);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarm_timer_nsleep - alarmtimer nanosleep
|
|
|
|
* @which_clock: clockid
|
2021-03-22 21:39:03 +00:00
|
|
|
* @flags: determines abstime or relative
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
* @tsreq: requested sleep time (abs or rel)
|
|
|
|
*
|
|
|
|
* Handles clock_nanosleep calls against _ALARM clockids
|
|
|
|
*/
|
|
|
|
static int alarm_timer_nsleep(const clockid_t which_clock, int flags,
|
2017-06-13 21:34:33 +00:00
|
|
|
const struct timespec64 *tsreq)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
{
|
|
|
|
enum alarmtimer_type type = clock2alarm(which_clock);
|
2017-06-07 08:42:27 +00:00
|
|
|
struct restart_block *restart = ¤t->restart_block;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
struct alarm alarm;
|
|
|
|
ktime_t exp;
|
2023-06-09 18:28:56 +00:00
|
|
|
int ret;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2011-06-17 01:47:37 +00:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
2019-09-03 17:18:02 +00:00
|
|
|
return -EOPNOTSUPP;
|
2011-06-17 01:47:37 +00:00
|
|
|
|
2014-07-07 21:06:11 +00:00
|
|
|
if (flags & ~TIMER_ABSTIME)
|
|
|
|
return -EINVAL;
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
if (!capable(CAP_WAKE_ALARM))
|
|
|
|
return -EPERM;
|
|
|
|
|
2018-03-26 13:29:57 +00:00
|
|
|
alarm_init_on_stack(&alarm, type, alarmtimer_nsleep_wakeup);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2017-03-26 19:04:18 +00:00
|
|
|
exp = timespec64_to_ktime(*tsreq);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
/* Convert (if necessary) to absolute time */
|
|
|
|
if (flags != TIMER_ABSTIME) {
|
2019-11-12 01:26:56 +00:00
|
|
|
ktime_t now = alarm_bases[type].get_ktime();
|
2018-07-02 07:34:29 +00:00
|
|
|
|
|
|
|
exp = ktime_add_safe(now, exp);
|
2019-11-12 01:27:04 +00:00
|
|
|
} else {
|
|
|
|
exp = timens_ktime_to_host(which_clock, exp);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
}
|
|
|
|
|
2017-06-07 08:42:27 +00:00
|
|
|
ret = alarmtimer_do_nsleep(&alarm, exp, type);
|
|
|
|
if (ret != -ERESTART_RESTARTBLOCK)
|
|
|
|
return ret;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
|
|
|
/* abs timers don't set remaining time or restart */
|
2017-06-07 08:42:27 +00:00
|
|
|
if (flags == TIMER_ABSTIME)
|
|
|
|
return -ERESTARTNOHAND;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2011-05-20 11:05:15 +00:00
|
|
|
restart->nanosleep.clockid = type;
|
2016-12-25 10:38:40 +00:00
|
|
|
restart->nanosleep.expires = exp;
|
2021-02-01 17:46:41 +00:00
|
|
|
set_restart_fn(restart, alarm_timer_nsleep_restart);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
return ret;
|
|
|
|
}
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2017-05-26 09:03:11 +00:00
|
|
|
const struct k_clock alarm_clock = {
|
2017-05-30 21:15:56 +00:00
|
|
|
.clock_getres = alarm_clock_getres,
|
2019-11-12 01:26:58 +00:00
|
|
|
.clock_get_ktime = alarm_clock_get_ktime,
|
2019-11-12 01:26:55 +00:00
|
|
|
.clock_get_timespec = alarm_clock_get_timespec,
|
2017-05-30 21:15:56 +00:00
|
|
|
.timer_create = alarm_timer_create,
|
2017-05-30 21:15:59 +00:00
|
|
|
.timer_set = common_timer_set,
|
|
|
|
.timer_del = common_timer_del,
|
|
|
|
.timer_get = common_timer_get,
|
2017-05-30 21:15:58 +00:00
|
|
|
.timer_arm = alarm_timer_arm,
|
2017-05-30 21:15:56 +00:00
|
|
|
.timer_rearm = alarm_timer_rearm,
|
|
|
|
.timer_forward = alarm_timer_forward,
|
|
|
|
.timer_remaining = alarm_timer_remaining,
|
2017-05-30 21:15:57 +00:00
|
|
|
.timer_try_to_cancel = alarm_timer_try_to_cancel,
|
2019-08-02 05:35:59 +00:00
|
|
|
.timer_wait_running = alarm_timer_wait_running,
|
2017-05-30 21:15:56 +00:00
|
|
|
.nsleep = alarm_timer_nsleep,
|
2017-05-26 09:03:11 +00:00
|
|
|
};
|
|
|
|
#endif /* CONFIG_POSIX_TIMERS */
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
|
|
|
|
/* Suspend hook structures */
|
|
|
|
static const struct dev_pm_ops alarmtimer_pm_ops = {
|
|
|
|
.suspend = alarmtimer_suspend,
|
2015-11-17 12:08:07 +00:00
|
|
|
.resume = alarmtimer_resume,
|
2011-01-11 17:42:13 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
static struct platform_driver alarmtimer_driver = {
|
|
|
|
.driver = {
|
|
|
|
.name = "alarmtimer",
|
|
|
|
.pm = &alarmtimer_pm_ops,
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2019-11-12 01:27:00 +00:00
|
|
|
static void get_boottime_timespec(struct timespec64 *tp)
|
|
|
|
{
|
|
|
|
ktime_get_boottime_ts64(tp);
|
|
|
|
timens_add_boottime(tp);
|
|
|
|
}
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
/**
|
|
|
|
* alarmtimer_init - Initialize alarm timer code
|
|
|
|
*
|
|
|
|
* This function initializes the alarm bases and registers
|
|
|
|
* the posix clock ids.
|
|
|
|
*/
|
|
|
|
static int __init alarmtimer_init(void)
|
|
|
|
{
|
2020-01-24 05:58:46 +00:00
|
|
|
int error;
|
2011-01-11 17:42:13 +00:00
|
|
|
int i;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-11 17:54:33 +00:00
|
|
|
|
2012-03-24 11:46:23 +00:00
|
|
|
alarmtimer_rtc_timer_init();
|
2012-03-23 22:52:25 +00:00
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
/* Initialize alarm bases */
|
|
|
|
alarm_bases[ALARM_REALTIME].base_clockid = CLOCK_REALTIME;
|
2019-11-12 01:26:56 +00:00
|
|
|
alarm_bases[ALARM_REALTIME].get_ktime = &ktime_get_real;
|
2020-08-18 06:26:51 +00:00
|
|
|
alarm_bases[ALARM_REALTIME].get_timespec = ktime_get_real_ts64;
|
2011-01-11 17:42:13 +00:00
|
|
|
alarm_bases[ALARM_BOOTTIME].base_clockid = CLOCK_BOOTTIME;
|
2019-11-12 01:26:56 +00:00
|
|
|
alarm_bases[ALARM_BOOTTIME].get_ktime = &ktime_get_boottime;
|
2019-11-12 01:27:00 +00:00
|
|
|
alarm_bases[ALARM_BOOTTIME].get_timespec = get_boottime_timespec;
|
2011-01-11 17:42:13 +00:00
|
|
|
for (i = 0; i < ALARM_NUMTYPE; i++) {
|
|
|
|
timerqueue_init_head(&alarm_bases[i].timerqueue);
|
|
|
|
spin_lock_init(&alarm_bases[i].lock);
|
|
|
|
}
|
2011-07-15 01:35:13 +00:00
|
|
|
|
2011-09-14 08:54:29 +00:00
|
|
|
error = alarmtimer_rtc_interface_setup();
|
|
|
|
if (error)
|
|
|
|
return error;
|
|
|
|
|
2011-01-11 17:42:13 +00:00
|
|
|
error = platform_driver_register(&alarmtimer_driver);
|
2011-09-14 08:54:29 +00:00
|
|
|
if (error)
|
|
|
|
goto out_if;
|
2011-01-11 17:42:13 +00:00
|
|
|
|
2011-09-14 08:54:29 +00:00
|
|
|
return 0;
|
|
|
|
out_if:
|
|
|
|
alarmtimer_rtc_interface_remove();
|
2011-01-11 17:42:13 +00:00
|
|
|
return error;
|
|
|
|
}
|
|
|
|
device_initcall(alarmtimer_init);
|