Breenix Interrupt and Syscall Path Development

CRITICAL PATH REQUIREMENTS - MANDATORY RULES

These requirements are NON-NEGOTIABLE. Violations will cause catastrophic performance degradation and subtle timing bugs that are extremely difficult to debug.

ABSOLUTELY FORBIDDEN in interrupt/syscall paths:

1. NO logging or serial output

   • No serial_println! or println! of any kind
   • No debug prints, trace messages, or diagnostics
   • This includes "temporary" debug code that you plan to remove later
   • EXCEPTION: Only in initialization code that runs once at boot, before interrupts are enabled

2. NO page table walks or memory diagnostics

   • No calls to translate_address() or similar
   • No memory allocation diagnostics
   • No stack usage analysis
   • No heap introspection