llext roadmap [WIP]

[pillo79]

After a chat with @teburd @edersondisouza @selescop at ZDS24, wishlist in no particular order:

• unified architecture relocation
• unified linking path
• kobject instantiation from the llext
• XIP
• security signing
• versioning / ABI for syscalls
• versioning for exported symbols, maybe subsys level?
• module information / init / done function
• ask for capabilities -> get assigned permissions
• limit extension to userspace
• filter syscalls
• inter-extension symbol linking

[github-actions]

Hi @pillo79! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[teburd]

After a discussion at EOSS, XIP could be implemented by providing a function that applies all relocations assuming given target addresses for storing the ELF sections. Not necessarily where those elf sections are in memory at the time of manipulation. I thought this was an incredible idea and I’m hopeful someone will contribute it.

[teburd]

I'd add supporting additional architectures to the list...

• x86
• riscv
• arc