Mercurial > nand-ecoscentric
comparison packages/kernel/current/doc/kernel.sgml @ 356:b77e86276ec3
* src/common/clock.cxx (add_alarm): Tweak last change to allow
alarm order for identical alarms to be the same as it used to be.
* src/common/clock.cxx (add_alarm): Fix bug resulting in alarms
not being added at all if a lower triggered alarm already exists.
Reported by Christoph Csebits.
Also fix bug when alarm is entered for the same time as tail.
These bugs only apply for CYGIMP_KERNEL_COUNTERS_SORT_LIST enabled.
* doc/kernel.sgml: document that order of callback for alarms at
identical times is unspecified.
| author | jlarmour |
|---|---|
| date | Tue, 01 Oct 2002 19:10:21 +0000 |
| parents | c9cbf5dfb306 |
| children | a65a4055f146 |
comparison
equal
deleted
inserted
replaced
| 355:115b5cde8e53 | 356:b77e86276ec3 |
|---|---|
| 2482 and will happen in the same context. If the alarm is associated with | 2482 and will happen in the same context. If the alarm is associated with |
| 2483 the system's real-time clock then this will be DSR context, following | 2483 the system's real-time clock then this will be DSR context, following |
| 2484 a clock interrupt. If the alarm is associated with some other | 2484 a clock interrupt. If the alarm is associated with some other |
| 2485 application-specific counter then the details will depend on how that | 2485 application-specific counter then the details will depend on how that |
| 2486 counter is updated. | 2486 counter is updated. |
| 2487 </para> | |
| 2488 <para> | |
| 2489 If two or more alarms are registered for precisely the same counter tick, | |
| 2490 the order of execution of the alarm functions is unspecified. | |
| 2487 </para> | 2491 </para> |
| 2488 </refsect1> | 2492 </refsect1> |
| 2489 | 2493 |
| 2490 <refsect1 id="kernel-alarms-context"><title>Valid contexts</title> | 2494 <refsect1 id="kernel-alarms-context"><title>Valid contexts</title> |
| 2491 <para> | 2495 <para> |