llext: add dynamic heap allocation support #90871
Merged
Conversation
This file contains hidden or 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
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
from
1a044f7 to
7f2e899
Compare
|
The change looks good, please add a test case so that it doesn't bitrot, should be fairly straightfoward |
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
from
2c8618f to
b079b09
Compare
teburd
previously approved these changes
May 30, 2025
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
from
b079b09 to
a3ae350
Compare
|
@pillo79, I added init/uninit calls, please take a look. |
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
from
a3ae350 to
01aa754
Compare
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
4 times, most recently
from
e49e450 to
62a9127
Compare
pillo79
reviewed
Jun 3, 2025
There was a problem hiding this comment.
Thanks! LGTM, just a sanity check and some wording suggestions. Also, would you mind adding a note for CONFIG_LLEXT_HEAP_DYNAMIC to this doc paragraph as well?
zephyr/doc/services/llext/config.rst
Lines 8 to 12 in 77c2c45
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
from
62a9127 to
db565ff
Compare
pillo79
reviewed
Jun 4, 2025
Some applications require loading extensions into the memory which does not exist during the boot time and cannot be allocated statically. Make the application responsible for LLEXT heap allocation. Do not allocate LLEXT heap statically. Signed-off-by: Alex Ivanov <[email protected]>
alexivanov-google
force-pushed
the
llext-heap-dynamic
branch
from
db565ff to
2c1995e
Compare
teburd
approved these changes
Jun 4, 2025
|
pillo79
approved these changes
Jun 4, 2025
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.
Some applications require loading extensions into the memory which does not exist during the boot time and cannot be allocated statically. Make the application responsible for LLEXT heap allocation. Do not allocate LLEXT heap statically.
This is created from and is a continuation of PR #90763.
TODO(@alexivanov-google): Comments to be addressed #90763 (comment)