| /Zephyr-4.3.0/kernel/ |
| D | CMakeLists.txt | 3 # kernel is a normal CMake library and not a zephyr_library because it
8 ${ZEPHYR_BASE}/include/zephyr/kernel.h
35 ${ZEPHYR_BASE}/include/zephyr/kernel/mm.h
41 ${ZEPHYR_BASE}/include/zephyr/kernel/mm/demand_paging.h
44 # If a pre-built static library containing kernel code exists in
53 add_library(kernel INTERFACE) target
54 target_link_libraries(kernel INTERFACE ${libkernel})
114 add_library(kernel ${kernel_files}) target
120 kernel
126 target_sources_ifdef(CONFIG_REQUIRES_STACK_CANARIES kernel PRIVATE compiler_stack_protect.c)
[all …]
|
| /Zephyr-4.3.0/scripts/footprint/ |
| D | plan.txt | 1 footprints,default,frdm_k64f,tests/benchmarks/footprints,,benchmark.kernel.footprints.default
2 …64f,tests/benchmarks/footprints,-DCONF_FILE=prj_userspace.conf,benchmark.kernel.footprints.userspa…
3 footprints,default,disco_l475_iot1,tests/benchmarks/footprints,,benchmark.kernel.footprints.default
4 …ot1,tests/benchmarks/footprints,-DCONF_FILE=prj_userspace.conf,benchmark.kernel.footprints.userspa…
5 footprints,default,nrf5340dk/nrf5340/cpuapp,tests/benchmarks/footprints,,benchmark.kernel.footprint…
6 footprints,default,nrf51dk/nrf51822,tests/benchmarks/footprints,,benchmark.kernel.footprints.default
7 footprints,default,hifive1_revb,tests/benchmarks/footprints,,benchmark.kernel.footprints.default
8 footprints,default,intel_ehl_crb,tests/benchmarks/footprints,,benchmark.kernel.footprints.default
9 …crb,tests/benchmarks/footprints,-DCONF_FILE=prj_userspace.conf,benchmark.kernel.footprints.userspa…
10 …gement,frdm_k64f,tests/benchmarks/footprints,-DCONF_FILE=prj_pm.conf,benchmark.kernel.footprints.pm
[all …]
|
| /Zephyr-4.3.0/tests/benchmarks/latency_measure/ |
| D | README.rst | 4 This benchmark measures the average latency of selected kernel capabilities,
32 * Kernel thread to kernel thread
34 * User thread to kernel thread
37 The default configuration builds only for the kernel. However, additional
63 …isr.resume.interrupted.thread.kernel - Return from ISR to interrupted thread : …
64 …isr.resume.different.thread.kernel - Return from ISR to another thread : …
65 …thread.create.kernel.from.kernel - Create thread : …
66 …thread.start.kernel.from.kernel - Start thread : …
67 …thread.suspend.kernel.from.kernel - Suspend thread : …
68 …thread.resume.kernel.from.kernel - Resume thread : …
[all …]
|
| /Zephyr-4.3.0/doc/kernel/usermode/ |
| D | overview.rst | 10 isolated from other user mode threads and from the kernel. A flawed or
12 of another thread or the kernel, and cannot interfere with or
13 control another user mode thread or the kernel.
17 - The kernel can protect against many unintentional programming errors which
20 - The kernel can sandbox complex data parsers such as interpreters, network
22 cannot compromise the kernel or other threads.
24 - The kernel can support the notion of multiple logical "applications", each
60 on read-only basis, kernel-wide. This policy may be adjusted.
65 - We prevent use of device drivers or kernel objects not specifically granted,
69 - We validate kernel or driver API calls with incorrect parameters that would
[all …]
|
| D | kernelobjects.rst | 6 A kernel object can be one of three classes of data:
8 * A core kernel object, such as a semaphore, thread, pipe, etc.
14 The set of known kernel objects and driver subsystems is defined in
18 with addresses to kernel objects when making API calls, but may never
20 All kernel objects must be placed in memory that is not accessible by
23 Since user threads may not directly manipulate kernel objects, all use of
25 a kernel object, checks are performed by system call handler functions
26 that the kernel object address is valid and that the calling thread
49 In order for a static kernel object to be usable by a user thread via system
50 call APIs, several conditions must be met on how the kernel object is declared:
[all …]
|
| /Zephyr-4.3.0/tests/subsys/portability/cmsis_rtos_v2/src/ |
| D | kernel.c | 30 version_i->os_info.kernel = osv.kernel; in get_version_check()
63 .os_info = {.api = 0xfefefefe, .kernel = 0xfdfdfdfd}, in ZTEST()
67 .os_info = {.api = 0xfcfcfcfc, .kernel = 0xfbfbfbfb}, in ZTEST()
77 zassert_equal(version.os_info.kernel, version_irq.os_info.kernel); in ZTEST()
|
| /Zephyr-4.3.0/subsys/shell/modules/kernel_service/ |
| D | kernel_shell.c | 9 SHELL_SUBCMD_SET_CREATE(kernel_cmds, (kernel));
10 SHELL_CMD_REGISTER(kernel, &kernel_cmds, "Kernel commands", NULL);
|
| /Zephyr-4.3.0/subsys/portability/cmsis_rtos_v2/ |
| D | kernel.c | 23 version->kernel = ver; in osKernelGetInfo()
28 SYS_KERNEL_VER_MAJOR(version->kernel), in osKernelGetInfo()
29 SYS_KERNEL_VER_MINOR(version->kernel), in osKernelGetInfo()
30 SYS_KERNEL_VER_PATCHLEVEL(version->kernel)); in osKernelGetInfo()
|
| D | CMakeLists.txt | 12 kernel.c
23 ${ZEPHYR_BASE}/kernel/include
|
| /Zephyr-4.3.0/include/zephyr/ |
| D | kernel_includes.h | 17 #error Please do not include kernel-specific headers directly, use <zephyr/kernel.h> instead
|
| /Zephyr-4.3.0/doc/kernel/services/threads/ |
| D | system_threads.rst | 10 A :dfn:`system thread` is a thread that the kernel spawns automatically
13 The kernel spawns the following system threads:
16 This thread performs kernel initialization, then calls the application's
20 priority (i.e. 0). If the kernel is not configured to support preemptible
24 The main thread is an essential thread while it is performing kernel
42 Additional system threads may also be spawned, depending on the kernel
54 kernel initialization is complete. The kernel does not pass any arguments
56 kernel passes arguments to it and ``main(int, char **)`` can be used.
|
| /Zephyr-4.3.0/samples/kernel/ |
| D | index.rst | 1 .. zephyr:code-sample-category:: kernel
6 These samples demonstrate how to use various kernel and scheduler features.
|
| /Zephyr-4.3.0/soc/nuvoton/numaker/m55m1x/ |
| D | sections.ld | 14 *(".noinit.*kernel/init.*")
15 *(".noinit.*kernel/mempool.*")
|
| /Zephyr-4.3.0/tests/subsys/random/rng/ |
| D | CMakeLists.txt | 7 zephyr_library_include_directories(${ZEPHYR_BASE}/kernel/include/)
13 ${ZEPHYR_BASE}/kernel/include
|
| /Zephyr-4.3.0/soc/egis/et171/common_linker/ |
| D | ram_start_nonzero.ld | 8 * Workaround for RAM_BASE is zero in XIP system, kernel object
10 * ex: tests/kernel/queue, k_queue_get() return k_queue address
|
| /Zephyr-4.3.0/soc/andestech/ae350/ |
| D | ram_start_nonzero.ld | 8 * Workaround for RAM_BASE is zero in XIP system, kernel object
10 * ex: tests/kernel/queue, k_queue_get() return k_queue address
|
| /Zephyr-4.3.0/include/zephyr/arch/x86/ |
| D | memory.ld | 11 * By default, the kernel is linked at its physical address and all addresses
22 * for all sections are relative to the base virtual address for the kernel.
32 #include <zephyr/kernel/mm.h>
38 /* Virtual base address for the kernel; with CONFIG_MMU this is not necessarily
51 /* "kernel RAM" for linker VMA allocations starts at the offset */
67 /* Physical RAM location where the kernel image is loaded */
79 #error Virtual kernel linking is not yet implemented for 64-bit
86 /* Address range where the kernel will be installed on a flash part (XIP),
93 /* Linear address range to link the kernel. If non-XIP, everything is
|
| /Zephyr-4.3.0/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 14 Default is to do 1:1 mapping for the kernel image (including code and data)
40 These are the Kconfigs that need to be enabled or defined for kernel to support
44 kernel.
53 * :kconfig:option:`CONFIG_KERNEL_VM_OFFSET`: kernel image starts at this offset
60 virtual and physical addresses, instead of kernel choosing addresses within
80 | main kernel |
112 script. This is the virtual address of the beginning of the kernel image at
116 script. This is the virtual address of the end of the kernel image at boot time.
127 is the end of the kernel image.
129 * ``K_MEM_VM_RESERVED`` is an area reserved to support kernel functions. For example,
[all …]
|
| /Zephyr-4.3.0/samples/synchronization/ |
| D | README.rst | 5 Manipulate basic kernel synchronization primitives.
10 A simple application that demonstrates basic sanity of the kernel.
13 are generated. This demonstrates that kernel scheduling, communication,
|
| /Zephyr-4.3.0/doc/releases/ |
| D | release-notes-1.6.rst | 6 We are pleased to announce the release of Zephyr kernel version 1.6.0. This
17 * Introduced the Unified Kernel; the nano and micro kernel were removed.
20 * Unified kernel documentation was added and legacy nanokernel/microkernel
31 * Introduced the unified kernel.
39 * Renamed kernel objects event to alert and memory map to memory slab.
118 * Modified build infrastructure to support unified kernel.
120 * Imported get_maintainer.pl from Linux kernel.
162 * Added Unified kernel API samples.
224 * ``ZEP-912`` - Finish renaming kernel object types
225 * ``ZEP-916`` - Eliminate kernel object API anomalies
[all …]
|
| D | release-notes-1.13.rst | 8 We are pleased to announce the release of Zephyr kernel version 1.13.0.
30 * Remove kernel event manager, replaced by generic tracing interface
31 * Enhanced Timeout and Tick handling in kernel
277 * Improve test coverage for the kernel
301 * :github:`9744` - tests/kernel/mbox/mbox_usage/testcase.yaml#kernel.mailbox crashes on ESP32
308 …github:`9683` - Multiple testcases in tests/kernel/mem_protect/mem_protect, tests/kernel/alert, te…
309 * :github:`9682` - tests/kernel/init: kernel.common.init.verify_bootdelay fails on sam_e70_xplained
317 * :github:`9664` - tests/kernel/threads/thread_apis/kernel.threads.user_mode crases on QEMU-x86
341 * :github:`9611` - tests/kernel/sched/schedule_api/testcase.yaml#kernel.sched.slice_reset fails on …
342 * :github:`9609` - tests/kernel/mem_protect/stack_random: kernel.memory_protection.stack_random fai…
[all …]
|
| /Zephyr-4.3.0/doc/kernel/services/other/ |
| D | float.rst | 6 The kernel allows threads to use floating point registers on board
16 The kernel does not support the use of floating point registers by ISRs.
25 The kernel can be configured to provide only the floating point services
27 which are described below. In addition, the kernel's support for the SSE
34 registers. It is the kernel's default floating point services mode.
37 the kernel generates a fatal error condition and aborts the thread.
45 On x86 platforms, the kernel initializes the floating point registers so they can
52 the floating point registers, as the kernel does not attempt to detect
60 the kernel supports one or more of the following thread sub-classes:
69 The kernel initializes and enables access to the floating point registers,
[all …]
|
| /Zephyr-4.3.0/doc/kernel/services/ |
| D | index.rst | 6 The Zephyr kernel lies at the heart of every Zephyr application. It provides
10 uses the kernel's features to create a complete application.
12 The configurable nature of the kernel allows you to incorporate only those
21 can also be developed using the Zephyr kernel. Examples of such systems
27 These pages cover basic kernel services related to thread scheduling and
51 These pages cover kernel objects which can be used to pass data between
118 These pages cover other kernel services.
|
| /Zephyr-4.3.0/drivers/timer/ |
| D | Kconfig.gecko | 13 kernel ticks instead of Cortex-M SysTick. You need this for system
18 Using BURTC instead of SysTick has a large impact on kernel timing
24 2. In general, accuracy of real-time scheduling by kernel will be
|
| /Zephyr-4.3.0/doc/connectivity/networking/api/ |
| D | traffic-class.rst | 19 specific kernel work queue. Each kernel work queue has a priority.
23 kernel work queue. The maximum number of traffic classes for both Rx and Tx
|
