#3264 closed defect (fixed)

Add monotonic watchdog based on uptime

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 5.1
Component: score Version: 5
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

The CLOCK_MONOTONIC time services use currently the clock tick based watchdog. This is a problem in case the uptime (measured via the timercounter) and the ticks since boot drift away (measured via the clock ticks). Introduce a new watchdog which uses the uptime. The memory overhead is quite small (two pointers per processor).

Change History (4)

comment:1 Changed on Feb 2, 2018 at 2:20:36 PM by Sebastian Huber <sebastian.huber@…>

In 89c0313/rtems:

score: Optimize watchdog tickle

Avoid unnecessary lock acquire/release operations. Get realtime via
timecounter only if necessary.

Update #3264.

comment:2 Changed on Feb 2, 2018 at 2:20:48 PM by Sebastian Huber <sebastian.huber@…>

In 3a4e044/rtems:

score: Rename _Watchdog_Realtime_from_*()

Rename _Watchdog_Realtime_from_*() to _Watchdog_Ticks_from_*().

Update #3264.

comment:3 Changed on Feb 2, 2018 at 2:21:00 PM by Sebastian Huber <sebastian.huber@…>

Resolution: fixed
Status: assignedclosed

In 9480815a/rtems:

score: Introduce new monotonic clock

Rename PER_CPU_WATCHDOG_MONOTONIC to PER_CPU_WATCHDOG_TICKS. Add new
PER_CPU_WATCHDOG_MONOTONIC which is based on the system uptime (measured
by timecounter).

Close #3264.

comment:4 Changed on Feb 5, 2018 at 10:39:52 AM by Sebastian Huber <sebastian.huber@…>

In a0633c5/rtems-libbsd:

SLEEPQUEUE(9): Update due to API changes

Update #3264.

Note: See TracTickets for help on using tickets.