summaryrefslogtreecommitdiffstats
path: root/kernel/time
diff options
context:
space:
mode:
authorJohn Stultz <john.stultz@linaro.org>2011-08-10 11:40:23 -0700
committerJohn Stultz <john.stultz@linaro.org>2011-08-10 14:55:24 -0700
commitd77e23accec56bf2ba12187fe77a2f500a511282 (patch)
treef6d875739df0e4c9b48628ce2eaad8581eb736b1 /kernel/time
parentdce75a8c71819ed4c7efdcd53c9b6f6356dc8cb5 (diff)
downloadop-kernel-dev-d77e23accec56bf2ba12187fe77a2f500a511282.zip
op-kernel-dev-d77e23accec56bf2ba12187fe77a2f500a511282.tar.gz
alarmtimers: Remove interval cap limit hack
Now that the alarmtimers code has been refactored, the interval cap limit can be removed. CC: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'kernel/time')
-rw-r--r--kernel/time/alarmtimer.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/kernel/time/alarmtimer.c b/kernel/time/alarmtimer.c
index f03b042..a522c00 100644
--- a/kernel/time/alarmtimer.c
+++ b/kernel/time/alarmtimer.c
@@ -525,15 +525,6 @@ static int alarm_timer_set(struct k_itimer *timr, int flags,
if (!rtcdev)
return -ENOTSUPP;
- /*
- * XXX HACK! Currently we can DOS a system if the interval
- * period on alarmtimers is too small. Cap the interval here
- * to 100us and solve this properly in a future patch! -jstultz
- */
- if ((new_setting->it_interval.tv_sec == 0) &&
- (new_setting->it_interval.tv_nsec < 100000))
- new_setting->it_interval.tv_nsec = 100000;
-
if (old_setting)
alarm_timer_get(timr, old_setting);
OpenPOWER on IntegriCloud