Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LLEXT: persistent dependency #9804

Draft
wants to merge 19 commits into
base: main
Choose a base branch
from
Draft

Conversation

lyakh
Copy link
Collaborator

@lyakh lyakh commented Jan 30, 2025

this should replace #9399

@lyakh lyakh force-pushed the depend-persist branch 2 times, most recently from 49dbeb1 to 2342b39 Compare January 31, 2025 09:42
lyakh added 2 commits January 31, 2025 10:57
Add a dedicated type for auxiliary LLEXT objects, not implementing
the Module Adapter API.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
llext_manager_link() doesn't the whole of struct module_data, it only
needs a pointer to a pointer to struct llext. Modify it to only
receive the scope, that it needs.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
lyakh added 16 commits February 3, 2025 14:24
The LLEXT context is currently bound to the Module Adapter API which
shouldn't be the case because we also need generic LLEXT-based
loadable SOF objects. This patch moves the context to struct
lib_manager_module which is safe, because the library manager is
always needed when dynamically loading modules.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Extract localisation and linking of a single LLEXT module into a
separate function, it will be re-used for auxiliary modules.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Currently lib_manager_module_free() first checks, if an LLEXT module
is being freed. If so, it first calls llext_unload() and then - if
the use-count is reported as zero, calls llext_manager_free_module().
Simplify this process by just calling llext_manager_free_module() and
letting it handle llext_unload() internally.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
This reverts commit cf31c9c. We do
now need to store BSS information for auxiliary LLEXT management.
When instantiating such a module for the second time, we don't have
access to Zephyr LLEXT information any more, so we need to use our
cached information for .bss allocation.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Auxiliary modules, implemented as LLEXT and used to provide
functionality for other modules, don't have TOML configuration, make
rimage skip that step for them.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Add comments to two structure fields, whose meaning isn't immediately
obvious otherwise.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
llext_manager_load_module()'s ebl argument is only used for .bss
alignment. Calculate it automatically to eliminate ebl, because it
isn't available during following loads. e.g. when reloading
dependencies.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Let llext_manager_mod_init() calculate mod_array itself internally,
it has all the data for that.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Currently when module's last instance is destroyed, it's freed and
its Zephyr context is destroyed too. At the same time the module is
kept in DRAM in a linked and relocated state, which means, that next
time when we have to use it, we need to tell Zephyr to instantiate it
while skipping the linking step. Additionally this makes handling
dependencies inconvenient: they are created during the linking step
by Zephyr and therefore are lost when the module is released. Then,
as described above, they're not recreated when the linking step is
skipped during a subsequent load.

To fix this problem this commit avoids destroying module's Zephyr
context when freeing. This costs around 200 bytes but makes handling
of dependencies possible.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Add support for auxiliary modules, exporting symbols to other
modules. In such cases Zephyr LLEXT API generates a dependency list,
available while the dependent module is loaded. SOF now preserves the
minimum module context even while it isn't used, that includes
dependency lists, so on a repeated load they're still available.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
FIR support code is used by eq-fir and by tdfb. When both of them are
built as LLEXT modules, FIR supporting functions can be dynamically
loaded too.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Test Zephyr PR zephyrproject-rtos/zephyr#84911
required for this one to work.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
This reverts commit dbdfe32.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Modular waves build seems to be broken even with a stub, disable it
until it's fixed.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Now that the Linux driver requirement for LLEXT dependencies has been
merged, we can test on any ACE architecture.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Fix a typo, making it impossible to build eq_fir without eq_iir as
LLEXT.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Modular TDFB needs additional exported symbols from Zephyr and SOF
core.

Signed-off-by: Guennadi Liakhovetski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant