doc: add two diagrams to user mode documentation
One shows how globals are routed for automatic memory domains. The other illustrates control flow when making system calls. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
parent
86461ac559
commit
cb87cc8fd6
4 changed files with 13 additions and 0 deletions
BIN
doc/reference/usermode/auto_mem_domain.png
Normal file
BIN
doc/reference/usermode/auto_mem_domain.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 238 KiB |
|
@ -213,6 +213,12 @@ contiguous block of memory, zero any BSS variables at boot, and define
|
|||
a memory partition of appropriate base address and size which contains all
|
||||
the tagged data.
|
||||
|
||||
.. figure:: auto_mem_domain.png
|
||||
:alt: Automatic Memory Domain build flow
|
||||
:align: center
|
||||
|
||||
Automatic Memory Domain build flow
|
||||
|
||||
Automatic memory partitions are only configured as read-write
|
||||
regions. They are defined with :c:macro:`K_APPMEM_PARTITION_DEFINE()`.
|
||||
Global variables are then routed to this partition using
|
||||
|
|
BIN
doc/reference/usermode/syscall_flow.png
Normal file
BIN
doc/reference/usermode/syscall_flow.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 151 KiB |
|
@ -170,6 +170,13 @@ necessary privilege elevation. In this layer, all arguments are treated as an
|
|||
unsigned 32-bit type. There is always a 32-bit unsigned return value, which
|
||||
may or may not be used.
|
||||
|
||||
.. figure:: syscall_flow.png
|
||||
:alt: System Call execution flow
|
||||
:width: 80%
|
||||
:align: center
|
||||
|
||||
System Call execution flow
|
||||
|
||||
Some system calls may have more than six arguments. The number of
|
||||
arguments passed via registers is limited to six for all
|
||||
architectures. Additional arguments will need to be passed in an array
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue