Repository navigation
0.10.0: standalone beneath a C library, openkal.exec, the interfaces under [kernel-abi] - #17
Merged
Merged
Conversation
…under [kernel-abi]; the example's board folded in
…andard error the console kal_alloc over-allocated every stricter alignment from the pool, so the 256 MiB a C library's allocator states for an arena cost 256 MiB of backed memory beyond the arena. An alignment of a page or more is now pages at an aligned address read from the memory map (AllocateAddress), the highest first; kal_free returns them as pages. OVMF's StdErr writes nothing to the serial console a runner reads, so diagnostics and abort messages were lost. A board defines okuefi_board_errors_to_console() to send standard error to ConOut; the example board does. The example checks a 256 MiB-aligned allocation.
Sunrisepeak
force-pushed
the
feat/0.10.0-exec
branch
from
November 13, 2026 13:36
82c3b69 to
ab6e950
Compare
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
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.
UEFI converges into openkal: the row
x86_64-uefiis served by openkal-platform 0.28.0 over openkal-musl 0.29.6 and openkal-llvm-runtime 0.20.3, with this implementation beneath them.standalone(feature):efi_mainrecords the firmware's tables and the arguments and hands the program to the C library's__libc_start_main, which runs the initialisers; without it the 0.9.0 behaviour stands. openkal-musl selects it oncfg(os = "uefi").openkal.exec: pages of typeEfiLoaderCode, protected through the memory attribute protocol where the firmware offers it (the ok-image runner carried as a UEFI application places code there).kal_exec_map_partanswers not supported (noopenkal.fs).[kernel-abi] provides-interfaces: 0.9.0 stated the list under[package], where the engine does not read it, so a consumer bound every interface.examples/board, a fixture; it was openkal-uefi-platform 0.1.0, whose content is folded here and into openkal-platform.Verified locally: the example built with mcpp 2026.11.12.1 boots under OVMF through dirun, every check holds, status 42. Beneath openkal-musl 0.29.6 and openkal-llvm-runtime 0.20.3 (mcpp 2026.11.13.1,
--release):import stdwithstd::printlnandstd::ranges::sortis a 1.2 MB EFI application that prints and returns 42 in 0.8 s.