<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/kernel/time/alarmtimer.c, branch v3.2.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/kernel/time/alarmtimer.c?h=v3.2.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/kernel/time/alarmtimer.c?h=v3.2.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-12-06T10:38:32Z</updated>
<entry>
<title>alarmtimers: Fix time comparison</title>
<updated>2011-12-06T10:38:32Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2011-12-05T20:20:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c9c024b3f3e07d087974db4c0dc46217fff3a6c0'/>
<id>urn:sha1:c9c024b3f3e07d087974db4c0dc46217fff3a6c0</id>
<content type='text'>
The expiry function compares the timer against current time and does
not expire the timer when the expiry time is &gt;= now. That's wrong. If
the timer is set for now, then it must expire.

Make the condition expiry &gt; now for breaking out the loop.

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Acked-by: John Stultz &lt;john.stultz@linaro.org&gt;
Cc: stable@kernel.org
</content>
</entry>
<entry>
<title>alarmtimers: Fix error handling</title>
<updated>2011-09-14T08:54:29Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2011-09-14T08:54:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4523f6ada86853750565c68e17126af2e3df9b8a'/>
<id>urn:sha1:4523f6ada86853750565c68e17126af2e3df9b8a</id>
<content type='text'>
commit 8bc0daf (alarmtimers: Rework RTC device selection using class
interface) did not implement required error checks. Add them.

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Rework RTC device selection using class interface</title>
<updated>2011-08-10T21:55:30Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-07-15T01:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8bc0dafb5cf38a19484dfb16e2c6d29e85820046'/>
<id>urn:sha1:8bc0dafb5cf38a19484dfb16e2c6d29e85820046</id>
<content type='text'>
This allows cleaner detection of the RTC device being registered, rather
then probing any time someone calls alarmtimer_get_rtcdev.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Add try_to_cancel functionality</title>
<updated>2011-08-10T21:55:29Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T19:41:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9082c465a5403f4a98734193e078552991a2e283'/>
<id>urn:sha1:9082c465a5403f4a98734193e078552991a2e283</id>
<content type='text'>
There's a number of edge cases when cancelling a alarm, so
to be sure we accurately do so, introduce try_to_cancel, which
returns proper failure errors if it cannot. Also modify cancel
to spin until the alarm is properly disabled.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Add more refined alarm state tracking</title>
<updated>2011-08-10T21:55:27Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T19:30:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a28cde81ab13cc251748a4c4ef06883dd09a10ea'/>
<id>urn:sha1:a28cde81ab13cc251748a4c4ef06883dd09a10ea</id>
<content type='text'>
In order to allow for functionality like try_to_cancel, add
more refined  state tracking (similar to hrtimers).

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Remove period from alarm structure</title>
<updated>2011-08-10T21:55:26Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T19:09:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9e26476243e438f4534a562660c1296a15a9e202'/>
<id>urn:sha1:9e26476243e438f4534a562660c1296a15a9e202</id>
<content type='text'>
Now that periodic alarmtimers are managed by the handler function,
remove the period value from the alarm structure and let the handlers
manage the interval on their own.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Remove interval cap limit hack</title>
<updated>2011-08-10T21:55:24Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T18:40:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d77e23accec56bf2ba12187fe77a2f500a511282'/>
<id>urn:sha1:d77e23accec56bf2ba12187fe77a2f500a511282</id>
<content type='text'>
Now that the alarmtimers code has been refactored, the interval
cap limit can be removed.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Add alarm_forward functionality</title>
<updated>2011-08-10T21:55:23Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T18:31:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dce75a8c71819ed4c7efdcd53c9b6f6356dc8cb5'/>
<id>urn:sha1:dce75a8c71819ed4c7efdcd53c9b6f6356dc8cb5</id>
<content type='text'>
In order to avoid wasting time expiring and re-adding very high freq
periodic alarmtimers, introduce alarm_forward() which is similar to
hrtimer_forward and moves the timer to the next future expiration time
and returns the number of overruns.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Push rearming peroidic timers down into alamrtimer handler</title>
<updated>2011-08-10T21:55:22Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T18:08:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=54da23b720d5d612f8f1669f9ed3744008fb7382'/>
<id>urn:sha1:54da23b720d5d612f8f1669f9ed3744008fb7382</id>
<content type='text'>
This patch pushes the periodic alarmtimer re-arming down into the alarmtimer
handler, mimicking how hrtimers handle this.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
<entry>
<title>alarmtimers: Change alarmtimer functions to return alarmtimer_restart values</title>
<updated>2011-08-10T21:55:20Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2011-08-10T17:37:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4b41308d2d0398409620613c7eaaaf52c738b042'/>
<id>urn:sha1:4b41308d2d0398409620613c7eaaaf52c738b042</id>
<content type='text'>
In order to properly fix the denial of service issue with high freq
periodic alarm timers, we need to push the re-arming logic into the
alarm timer handler, much as the hrtimer code does.

This patch introduces alarmtimer_restart enum and changes the
alarmtimer handler declarations to use it as a return value. Further,
to ease following changes, it extends the alarmtimer handler functions
to also take the time at expiration. No logic is yet modified.

CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
</content>
</entry>
</feed>
