Thank you for reply.
On 2021/09/08 16:22, Yasushi SHOJI wrote:
Hi,Currently, No. I'm trying to add a support for CONFIG_USE_SWITCH=y case.
Sorry for confusing. Older means CONFIG_USE_SWITCH=n.Newer switching sets NEW thread handle into _current_cpu.current BEFORE calling arch_switch().AFAICS, even with v1.11, we are setting `_current` to `new_thread` in
Does not means Zephyr's version.
Why do you `use _current_cpu` at all? `_arch_switch()` orBecause to keep consistency for another context switching (by preemption) and
Only _current_cpu.current is available when an interrupt occurred.