llext: manager: use k_ssize_t instead of ssize_t #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Set min. cmake version required to what zephyr uses. Signed-off-by: Anas Nashif <[email protected]>
`z_arch_esf_t` has been deprecated, use `struct arch_esf` instead. Signed-off-by: Yong Cong Sin <[email protected]>
Renames arch_sched_ipi() to arch_sched_broadcast_ipi() to reflect recent changes from the IPI optimization work done in Zephyr. Signed-off-by: Peter Mitsis <[email protected]>
Re-group headers more logically in eq_iir.c and mixin_mixout.c. Signed-off-by: Guennadi Liakhovetski <[email protected]>
When dynamically mapping memory, we need to update access flags according to the type of the mapping. Signed-off-by: Guennadi Liakhovetski <[email protected]>
When an LLEXT module contains multiple Module Adapter instances, their manifests are stored in an array in the .module section. Those array entries contain per-instance information like module entry points, names, UUIDs, but ELF information is common for all instances. Store it in the first array entry to avoid confusion. Signed-off-by: Guennadi Liakhovetski <[email protected]>
We map memory pages for loaded modules dynamically and we're able to set memory flags for write access or for code execution. This commit takes advantage of the recently added section grouping and maps the three module parts separately: executable code, read-only data and writable data, including zero-initialised .bss. This also cleans up references, pointing into module storage in IMR instead of the mapped addresses. Signed-off-by: Guennadi Liakhovetski <[email protected]>
Zephyr places .bss into a separate section element, still if it's immediately adjacent to writable data we can merge and allocate them together. Signed-off-by: Guennadi Liakhovetski <[email protected]>
This change accompanies a similar Zephyr change where we create explicit k-types to avoid using POSIX types below the line in where the POSIX API sits in our stack, thus avoiding a dependency cycle. Additional types we should avoid using (as well as the <sys/types.h> header itself) are listed on the opengroup website (search for "sys/types.h"). Signed-off-by: Christopher Friedt <[email protected]>
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change accompanies a similar Zephyr change where we create explicit k-types to avoid using POSIX types below the line where the POSIX API sits in our stack, thus avoiding a dependency cycle.
Additional types we should avoid using in the kernel, core os, and os services (as well as the
<sys/types.h>header itself) are listed here