michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: posix: overview: link to memory domain documentation

Browse source 
Link to the Memory Domains document in the overview.

Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
This commit is contained in:
Chris Friedt 2024-05-02 19:45:41 -04:00 • committed by Anas Nashif
commit b2954ab036
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/services/portability/posix/overview/index.rst
View file

@ -41,9 +41,10 @@ POSIX Subprofiles
While Zephyr supports running multiple :ref:`threads <threads_v2>` (possibly in an
:ref:`SMP <smp_arch>` configuration), as well as
:ref:`Virtual Memory and MMUs <memory_management_api>`, Zephyr code and data normally share a
common address space. The Zephyr kernel executable code and the application executable code are
typically compiled into the same binary artifact. From that perspective, Zephyr apps can be seen
as running in the context of a single process.
common address space that is partitioned into separate :ref:`Memory Domains <memory_domain>`. The
Zephyr kernel executable code and the application executable code are typically compiled into the
same binary artifact. From that perspective, Zephyr apps can be seen as running in the context of
a single process.
While multi-purpose operating systems (OS) offer full POSIX conformance, Real-Time Operating
Systems (RTOS) such as Zephyr typically serve a fixed-purpose, have limited hardware resources,