Skip to content

Conversation

@zephyrbot
Copy link

@zephyrbot zephyrbot commented Sep 16, 2024

Backport da5f7e1~2..da5f7e1 from #75832.

Fixes #75834

This adds a spinlock to make sure writing to hardware MPU
regions is atomic, and cannot be interrupted until all
regions are written to hardware.

Signed-off-by: Daniel Leung <daniel.leung@intel.com>
(cherry picked from commit 6bd0dcf)
If adding/removing to the domain of the current running
thread, we need to update the hardware MPU regions or else
the addition or removal would not be reflected to current
running thread.

Signed-off-by: Daniel Leung <daniel.leung@intel.com>
(cherry picked from commit da5f7e1)
@zephyrbot zephyrbot added Backport Backport PR and backport failure issues area: Xtensa Xtensa Architecture labels Sep 16, 2024
@henrikbrixandersen henrikbrixandersen added this to the v3.7.1 milestone Nov 4, 2024
@nashif nashif merged commit db2df71 into v3.7-branch Nov 4, 2024
@nashif nashif deleted the backport-75832-to-v3.7-branch branch November 4, 2024 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Xtensa Xtensa Architecture Backport Backport PR and backport failure issues

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

xtensa: mpu: adding or removing partitions from memory domain of current running thread has no effect

6 participants