summaryrefslogtreecommitdiffstats
path: root/cpukit/score/src/coretodget.c
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2013-07-31 13:30:42 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2013-08-01 16:45:46 +0200
commit9bf74673f928788b0ea4addabf045b94844d40ff (patch)
tree495ca384343769feefd96f88061ccc5ed5f192bb /cpukit/score/src/coretodget.c
parentscore: Move nanoseconds since last tick support (diff)
downloadrtems-9bf74673f928788b0ea4addabf045b94844d40ff.tar.bz2
score: Use an ISR lock for TOD
Two issues are addressed. 1. On single processor configurations the set/get of the now/uptime timestamps is now consistently protected by ISR disable/enable sequences. Previously nested interrupts could observe partially written values since 64-bit writes are not atomic on 32-bit architectures in general. This could lead to non-monotonic uptime timestamps. 2. The TOD now/uptime maintanence is now independent of the giant lock. This is the first step to remove the giant lock in _Thread_Dispatch().
Diffstat (limited to 'cpukit/score/src/coretodget.c')
-rw-r--r--cpukit/score/src/coretodget.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/cpukit/score/src/coretodget.c b/cpukit/score/src/coretodget.c
index 50262fd2f5..50ca8a0029 100644
--- a/cpukit/score/src/coretodget.c
+++ b/cpukit/score/src/coretodget.c
@@ -32,10 +32,10 @@ Timestamp_Control *_TOD_Get_with_nanoseconds(
Timestamp_Control now;
uint32_t nanoseconds;
- _ISR_Disable( level );
+ _TOD_Acquire( tod, level );
nanoseconds = ( *tod->nanoseconds_since_last_tick )();
now = *clock;
- _ISR_Enable( level );
+ _TOD_Release( tod, level );
_Timestamp_Set( &offset, 0, nanoseconds );
_Timestamp_Add_to( &now, &offset );