Split the implementation of supercall

[mirxin]

Summary

This PR refactors the relationship between kernelpatch and supercall by removing the hardcoded supercall implementation from the core service and reimplementing it as an optional Kernel Patch Module (KPM).

Motivation

Currently, kernelpatch serves as the core infrastructure provider for kernel patching. However, it remains tightly coupled with supercall—a higher-level functional component. This coupling introduces unnecessary dependencies and reduces the clarity of the core service’s responsibilities.

To maintain a clean and maintainable architecture, kernelpatch should focus solely on providing the most essential capability: loading and managing Kernel Patch Modules (KPMs).

Proposed Changes

• Remove supercall implementation from the kernelpatch core codebase.
• Reimplement supercall functionality as a standalone KPM module.
• Update documentation and examples to reflect the new modular approach.

Benefits

Benefit	Description
Decoupling	Core service is no longer tied to specific functional implementations.
Maintainability	Easier to update or replace supercall without modifying the core.
Extensibility	Other functional components can follow the same KPM-based pattern.
Clarity	Clear separation between infrastructure (kernelpatch) and features (supercall).

Trade-off

• Additional installation step: Users must now install the supercall KPM module separately if they need the functionality. This is a one-time, straightforward process.

Checklist

• Remove supercall references from core code
• Create supercall.kpm module
• Necessary testing [early stage]
• Handled exported symbols to pass tests
• Necessary testing
• Update build system accordingly
• Update documentation and usage examples
• Add migration guide for existing users

[mirxin]

已完成概念验证 | Concept validation completed

---

****