Priority inheritance behavior in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is priority inheritance in FreeRTOS?

Priority inheritance is a mechanism where a lower-priority task temporarily inherits the higher priority of a task it blocks, to prevent priority inversion.

beginner

Why is priority inheritance important in real-time systems?

It prevents priority inversion, where a high-priority task waits too long because a low-priority task holds a resource it needs.

intermediate

How does FreeRTOS implement priority inheritance with mutexes?

When a high-priority task tries to take a mutex held by a lower-priority task, the lower-priority task temporarily inherits the higher priority until it releases the mutex.

intermediate

What happens if multiple higher-priority tasks block on the same mutex in FreeRTOS?

The task holding the mutex inherits the highest priority among all blocked higher-priority tasks until it releases the mutex.

advanced

Can priority inheritance cause deadlocks in FreeRTOS?

Priority inheritance itself does not cause deadlocks, but improper use of mutexes and resource locking can lead to deadlocks.

What problem does priority inheritance solve in FreeRTOS?

A Priority inversion

B Memory leaks

C Task starvation

D Stack overflow

Priority inheritance prevents priority inversion where a high-priority task is blocked by a lower-priority task holding a resource.

When does a task inherit a higher priority in FreeRTOS?

A When it blocks on a semaphore

B When it holds a mutex needed by a higher-priority task

C When it is created

D When it finishes execution

A task holding a mutex inherits the highest priority of any higher-priority task blocked on that mutex.

What happens to the priority of a task after it releases the mutex in FreeRTOS?

A It stays at the inherited priority

B It becomes the lowest priority

C It returns to its original priority

D It becomes the highest priority in the system

After releasing the mutex, the task's priority returns to its original value.

Which FreeRTOS object supports priority inheritance?

A Mutex

B Counting semaphore

C Queue

D Binary semaphore

Only mutexes in FreeRTOS implement priority inheritance to avoid priority inversion.

Can priority inheritance completely eliminate priority inversion?

A Yes, but only for binary semaphores

B Yes, always

C No, it makes it worse

D No, but it reduces its impact

Priority inheritance reduces priority inversion but does not eliminate all possible delays.

Explain how priority inheritance works in FreeRTOS when a high-priority task waits for a mutex held by a low-priority task.

Think about how the system avoids the high-priority task waiting too long.

Describe the role of mutexes in priority inheritance behavior in FreeRTOS.

Focus on the synchronization object that triggers priority inheritance.

Practice

1. What is the main purpose of priority inheritance in FreeRTOS?

easy

A. To increase the priority of all tasks equally

B. To prevent low priority tasks from blocking high priority tasks for too long

C. To allow tasks to run in a random order

D. To disable task scheduling temporarily

Solution

1. Step 1: Understand priority inversion problem

   Priority inversion happens when a low priority task holds a resource needed by a high priority task, causing delays.

2. Step 2: Role of priority inheritance

   Priority inheritance temporarily raises the low priority task's priority to the high priority task's level to reduce blocking time.

3. Final Answer:

   To prevent low priority tasks from blocking high priority tasks for too long -> Option B

4. Quick Check:

   Priority inheritance prevents blocking = A [OK]

Hint: Priority inheritance helps high priority tasks run faster [OK]

Common Mistakes:

• Thinking it raises all tasks' priorities
• Confusing it with disabling scheduling
• Believing it randomizes task order

2. Which FreeRTOS synchronization primitive automatically supports priority inheritance?

easy

A. Semaphore (binary)

B. Event group

C. Mutex

D. Queue

Solution

1. Step 1: Identify synchronization primitives

   FreeRTOS offers semaphores, mutexes, queues, and event groups for task synchronization.

2. Step 2: Check which supports priority inheritance

   Mutexes in FreeRTOS implement priority inheritance automatically to avoid priority inversion.

3. Final Answer:

   Mutex -> Option C

4. Quick Check:

   Mutex = priority inheritance support [OK]

Hint: Mutexes handle priority inheritance automatically [OK]

Common Mistakes:

• Choosing binary semaphore which lacks priority inheritance
• Confusing queues or event groups with mutexes
• Assuming all synchronization primitives support priority inheritance

3. Consider three tasks: High, Medium, and Low priority. Low holds a mutex needed by High. Medium is ready to run. What happens when priority inheritance is enabled?

medium

A. Medium task runs before Low and High

B. Low task is blocked until Medium finishes

C. High task runs immediately, ignoring mutex

D. Low task inherits High priority, runs before Medium

Solution

1. Step 1: Analyze priority inversion scenario

   Low priority task holds mutex needed by High priority task, but Medium priority task is ready.

2. Step 2: Effect of priority inheritance

   Low task temporarily inherits High priority, so it runs before Medium to release mutex faster.

3. Final Answer:

   Low task inherits High priority, runs before Medium -> Option D

4. Quick Check:

   Priority inheritance boosts Low task priority = B [OK]

Hint: Low task runs at High priority to unblock High task [OK]

Common Mistakes:

• Assuming Medium runs before Low despite inheritance
• Thinking High runs without mutex
• Believing Low is blocked by Medium

4. You wrote code using a binary semaphore to protect a shared resource, but high priority tasks are blocked too long. What is the likely issue?

medium

A. Binary semaphore does not support priority inheritance

B. Mutex was not created properly

C. High priority tasks are not using the semaphore

D. Task priorities are all equal

Solution

1. Step 1: Identify synchronization primitive used

   Binary semaphore is used to protect shared resource.

2. Step 2: Check priority inheritance support

   Binary semaphores do not support priority inheritance, causing priority inversion issues.

3. Final Answer:

   Binary semaphore does not support priority inheritance -> Option A

4. Quick Check:

   Binary semaphore lacks priority inheritance = A [OK]

Hint: Use mutex, not binary semaphore, for priority inheritance [OK]

Common Mistakes:

• Assuming binary semaphore supports priority inheritance
• Blaming task priorities without checking synchronization
• Ignoring mutex creation correctness

5. In a system with tasks A (priority 3), B (priority 2), and C (priority 1), task C holds a mutex needed by A. Task B is CPU intensive. How does FreeRTOS priority inheritance help avoid priority inversion here?

hard

A. Task C temporarily inherits priority 3, preempting B to release mutex faster

B. Task B inherits priority 3 to run before C and A

C. Task A runs without waiting for mutex

D. Task C is blocked until B finishes

Solution

1. Step 1: Understand task priorities and mutex ownership

   Task C (low priority) holds mutex needed by Task A (high priority), while Task B (medium priority) is CPU intensive.

2. Step 2: Apply priority inheritance behavior

   Task C inherits Task A's high priority (3) temporarily, allowing it to preempt Task B and release the mutex quickly.

3. Final Answer:

   Task C temporarily inherits priority 3, preempting B to release mutex faster -> Option A

4. Quick Check:

   Priority inheritance boosts C to A's priority = C [OK]

Hint: Low priority task inherits high priority to beat medium task [OK]

Common Mistakes:

• Thinking medium priority task inherits high priority
• Assuming high priority task runs without mutex
• Believing low priority task is blocked by medium task