Mutex attribute functions */

Register pthread_t* by UTCB address (called by pthread_entry_wrapper). * Returns 0 on success, -1 if thread_ptr_table is full. * When table is full,

Main test runner */

Run QEMU and parse test output. Args: elf_path: Path to the ELF file timeout: Timeout in seconds Returns: TestR

Run QEMU for fault tests (expecting kernel panic). Args: elf_path: Path to the ELF file timeout: Timeout in seconds Ret

Main test runner */

* Initialize scheduler link to "not queued" state. * NULL pointers indicate thread is not in any queue. */

* Change thread preemption threshold (PTS). * * Threshold controls which priorities can preempt this thread: * - Lower threshold = fewer threads

* Main scheduler entry point. * Selects next thread and switches to it. */

* Select next thread to run with PTS enforcement. * * O(1) selection: CLZ gives highest priority, return queue head. * Strict invariant: all queued

* Read one character via semihosting (blocking) */

Basic spinlock ops for ARMv7M architecture */

* Notification clear syscall handler. * Clears specified notification bits from calling thread (non-blocking). * * Parameters: * R0: bits - noti

* Notification post syscall handler. * Signals notification bits to target thread. * * Parameters: * R0: target_tid - thread to notify (global I

* Notification wait syscall handler. * Blocks caller until any notification bits in mask are set. * * Parameters: * R0: mask - notification bits

* Schedule system call handler. * Implements L4 Schedule interface with PTS support. * * Parameters (from L4 spec): * R0: dest - target thread I

* Timer notification syscall handler. * Creates a timer that delivers notifications to the calling thread. * * Parameters: * R0: ticks - timer d

Test 3: IRQ latency measurement */

Test 2: FPU lazy context stacking */

Test 1: MPU region configuration */

Test 4: PendSV-based context switching */

Test 6: Stack alignment (AAPCS requires 8-byte alignment at call sites) */

Test 7: Unaligned memory access handling */

Test 5: UTCB alignment (must be word-aligned) */

Test 6: Cross-address-space query (if supported) */

Test 1: L4_Stop functionality */

Test 4: Set/get pager via ExchangeRegisters */

Test 2: L4_Start functionality */

Test 3: Read SP/IP from thread */

Test 5: Query thread status */

* Basic IPC test: sender sends a message, receiver receives it. * Validates: sender TID, message label, message content. */

Test 10: Aborted IPC error (receive phase) */

Test 9: Aborted IPC error (send phase) */

Test 4: Cancelled IPC error (receive phase) */

Test 3: Cancelled IPC error (send phase) */

Test 2: Non-existent partner (receive phase) */

Test 1: Non-existent partner (send phase) */

Test 5: Message overflow error (send phase) */

Test 7: Timeout on current thread's receive */

Test 8: Timeout waiting for specific partner */

Test 6: Timeout from sender side */

Test 4: Abort IPC on unresolvable pagefault */

Test 3: Map and retry after pagefault */

Test 2: Pagefault on receive side */

Test 1: Pagefault on unmapped memory during IPC */

* IPC Timeout Receive Test * * Wait for a message with timeout when no sender exists. * Should return with timeout error after the specified period

* IPC Timeout Send Test * * Send to a thread that doesn't exist with a short timeout. * The IPC should fail with timeout error, not hang forever.

* Test: Verify user-space interrupt handling works. * Requires CONFIG_EXTI0_USER_IRQ and CONFIG_EXTI1_USER_IRQ. */

* Test: Verify L4_GetKernelInterface() returns valid KIP. */

* Test: Verify L4_NumProcessors() returns at least 1. */

Test 2: Memory grant operation */

Test 7: Invalid memory operations */

Test 1: Memory map operation */

Test 9: MPU region cleanup */

Test 8: MPU region exhaustion */

Test 3: Memory rights verification */

Test 5: Memory sharing between threads */

Test 4: Memory unmap operation */

Test 6: Cross-address-space memory write */

* Demonstration: Unified notification system architecture. * * This test documents the complete notification flow: */

* Test: Verify multiple concurrent timer creation. * * Creates multiple timers with different notification bits. * Tests: * - Multiple timer creat

* Test: Document notification statistics via KDB. * * This test documents that KDB 'N' command should show * notification activity after the timer

* Test: Verify basic timer notification creation. * * Creates a one-shot timer that delivers notification via the unified * notification system. Te