Architecture Interface

Internal kernel APIs with public scope More...

Topics
	Architecture thread APIs
	Architecture timing APIs
	Architecture-specific IRQ APIs
	Architecture-specific SMP APIs
	Architecture-specific Stack Walk APIs
	To add API support to an architecture, arch_stack_walk() should be implemented and a non-user configurable Kconfig ARCH_HAS_STACKWALK that is default to y should be created in the architecture's top level Kconfig, with all the relevant dependencies.
	Architecture-specific Thread Local Storage APIs
	Architecture-specific core dump APIs
	Architecture-specific gdbstub APIs
	Architecture-specific memory-mapping APIs
	Architecture-specific power management APIs
	Architecture-specific userspace APIs
	Miscellaneous architecture APIs
	Xtensa APIs

Detailed Description

Internal kernel APIs with public scope

Any public kernel APIs that are implemented as inline functions and need to call architecture-specific API so will have the prototypes for the architecture-specific APIs here. Architecture APIs that aren't used in this way go in kernel/include/kernel_arch_interface.h.

The set of architecture-specific APIs used internally by public macros and inline functions in public headers are also specified and documented.

For all macros and inline function prototypes described herein, <arch/cpu.h> must eventually pull in full definitions for all of them (the actual macro defines and inline function bodies)

include/kernel.h and other public headers depend on definitions in this header.