Avoid division by zero in posix targets #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The tick duration in microseconds may be calculated to zero depending on the processor clock speed. This patch sets it to 1 if the value is 0. Signed-off-by: Vinicius Tinti <[email protected]>
Map all OSAL internal types to common types already defined in <stdint.h>. Also adding support for x86_64. Signed-off-by: Vinicius Tinti <[email protected]>
The OSAL api uses a global lock to perform some operations using mutex,
semaphores, queues and so. This leads to a possible deadlock in the program
due the following situation.
Let "I" be the timer interrupt (SIG63):
|[Thread 1]
| ...
| call OS_TaskGetInfo
| ...
| lock(global)
| ...
I----+--------------------+
|[Interrupt]
| ...
| call OS_TaskGetInfo
| ...
| lock(global) // DEADLOCK
There are some possible solutions to avoid this problem. One is to never use any
OSAL primitives on the interrupt context, which quite limit the library. Other
would be block all signals during the global lock and let them be pending. This
approach may introduce poor performance. Other would be find out how to remove
these global locks. Another could be use safe locks on interrupt handler.
This patch implements the blocking signals solution because it is the best
trade-off of the current solutions.
There is also a single special case which is not handled by this patch.
Signed-off-by: Vinicius Tinti <[email protected]>
Signed-off-by: Vinicius Tinti <[email protected]>
Signed-off-by: Vinicius Tinti <[email protected]>
|
This change is obsolete, wrote #12 to address this issue in the context of the current code base. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tick duration in microseconds may be calculated to zero depending on the
processor clock speed.
Maybe another solution could be using BogoMips for calculating the tick duration or even querying sysfs (i.e. /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq). Both have drawbacks and in some case zero will be get as a result.
Also BogoMips has recently change and now it can be specified at build time.