zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Nicolas Pitre	46aa6717ff	Revert "arch: deprecate `_current`" Mostly a revert of commit `b1def7145f` ("arch: deprecate `_current`"). This commit was part of PR #80716 whose initial purpose was about providing an architecture specific optimization for _current. The actual deprecation was sneaked in later on without proper discussion. The Zephyr core always used _current before and that was fine. It is quite prevalent as well and the alternative is proving rather verbose. Furthermore, as a concept, the "current thread" is not something that is necessarily architecture specific. Therefore the primary abstraction should not carry the arch_ prefix. Hence this revert. Signed-off-by: Nicolas Pitre <npitre@baylibre.com>	6 months ago
Yong Cong Sin	b1def7145f	arch: deprecate `_current` `_current` is now functionally equals to `arch_curr_thread()`, remove its usage in-tree and deprecate it instead of removing it outright, as it has been with us since forever. Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>	8 months ago
Peter Mitsis	0bcdae2c62	kernel: Add CONFIG_ARCH_HAS_DIRECTED_IPIS Platforms that support IPIs allow them to be broadcast via the new arch_sched_broadcast_ipi() routine (replacing arch_sched_ipi()). Those that also allow IPIs to be directed to specific CPUs may use arch_sched_directed_ipi() to do so. As the kernel has the capability to track which CPUs may need an IPI (see CONFIG_IPI_OPTIMIZE), this commit updates the signalling of tracked IPIs to use the directed version if supported; otherwise they continue to use the broadcast version. Platforms that allow directed IPIs may see a significant reduction in the number of IPI related ISRs when CONFIG_IPI_OPTIMIZE is enabled and the number of CPUs increases. These platforms can be identified by the Kconfig option CONFIG_ARCH_HAS_DIRECTED_IPIS. Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>	1 year ago
Peter Mitsis	d8a4c8a90c	kernel: Add CONFIG_IPI_OPTIMIZE The CONFIG_IPI_OPTIMIZE configuration option allows for the flagging and subsequent signaling of IPIs to be optimized. It does this by making each bit in the kernel's pending_ipi field a flag that indicates whether the corresponding CPU might need an IPI to trigger the scheduling of a new thread on that CPU. When a new thread is made ready, we compare that thread against each of the threads currently executing on the other CPUs. If there is a chance that that thread should preempt the thread on the other CPU then we flag that an IPI is needed for that CPU. That is, a clear bit indicates that the CPU absolutely will not need to reschedule, while a set bit indicates that the target CPU must make that determination for itself. Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>	1 year ago
Anas Nashif	0b473ce925	kernel: rename sliceable -> thread_is_sliceable Trivial rename of sliceable function. Signed-off-by: Anas Nashif <anas.nashif@intel.com>	1 year ago
Anas Nashif	37df485463	kernel: split timeslicing/ipi code out of sched.c Move both timeslicing and IPI code to own files. Signed-off-by: Anas Nashif <anas.nashif@intel.com>	1 year ago