From 83810ee3fc55e7a63794d554417caf55a3293274 Mon Sep 17 00:00:00 2001 From: Per Lindgren Date: Sat, 28 Sep 2019 21:45:54 +0200 Subject: [PATCH] Lock Optimization RFC (Notes updated) --- Notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Notes.md b/Notes.md index 341a3e4125..c4cb9db054 100644 --- a/Notes.md +++ b/Notes.md @@ -3,7 +3,7 @@ ## Idea We are reading BASEPRI independently if and only if we are actually changing BASEPRI. -On restoring BASEPRI chose to restore read value if at the outmost nesting level (initial priority of the task). In this way, unnecessary BASEPRI accesses, and reduce register pressure. +On restoring BASEPRI chose to restore read value if at the outmost nesting level (initial priority of the task). In this way, we can avoid unnecessary BASEPRI accesses, and reduce register pressure. If you want to play around checkout the `lockopt` branch and use: