#1481 closed defect (fixed)

Check for partial period performed too early when updating period statistics

Reported by: Glenn Humphrey Owned by: Glenn Humphrey
Priority: normal Milestone: 4.10
Component: score Version: 4.9
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

When the period statistics are updated prior to blocking for the next period, a check is performed to see if the cpu usage had been reset since the period was initiated. If a reset had been performed, the update must be skipped because the information is incorrect to make a valid calculation. The check was performed before accounting for the cpu used since last contact switch (nanosecond timing only). This very often caused the first call to update to be skipped and thus produced erroneous average times.

This bug was discovered during re-work on the head of the ratemonotonic functions. This bug only applies to 4.9.

Attachments (1)

pr1481-49.diff (1.2 KB) - added by Glenn Humphrey on Dec 11, 2009 at 8:57:47 PM.
Patch for 4.9

Download all attachments as: .zip

Change History (2)

Changed on Dec 11, 2009 at 8:57:47 PM by Glenn Humphrey

Attachment: pr1481-49.diff added

Patch for 4.9

comment:1 Changed on Dec 11, 2009 at 9:04:09 PM by Glenn Humphrey

Resolution: fixed
Status: newclosed

Patch committed.

Note: See TracTickets for help on using tickets.