285c5b26dd
This was a little embarassing. The swap code got this right, and the interrupt exit path got it right, but on entry we weren't ever saving the shift and loop registers for the interrupted context. This almost always worked anyway as the loop registers aren't ever used in any Zephyr code (gcc won't generate this style of loop AFAICT) and the SAR shift amount register is generally used only in two pairs of adjacent instructions making the chance of hitting that exact cycle quite low in general. But of course we have shift-happy crypto code in our tests, so this got caught, thankfully. See https://github.com/zephyrproject-rtos/zephyr/issues/6470 Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| kernel_arch_data.h | ||
| kernel_arch_func.h | ||
| kernel_arch_thread.h | ||
| kernel_event_logger_arch.h | ||
| offsets_short_arch.h | ||
| xtensa-asm2-context.h | ||
| xtensa-asm2-s.h | ||
| xtensa-asm2.h | ||
| xtensa_api.h | ||
| xtensa_config.h | ||
| xtensa_context.h | ||
| xtensa_rtos.h | ||
| xtensa_timer.h | ||