ebpf-for-windows VS lai

There already is an eBPF for Windows, it's even Microsoft's own project https://github.com/microsoft/ebpf-for-windows

This link is about a proposed new eBPF verifier for the Linux kernel that doesn't use signing. As a research project it is not integrated to the kernel, but their plan does not involve trusting user space (instead they suggest doing the heavy lifting of the verification in user space and provide a proof of safety that the kernel checks, which seems sensible to me).

I believe you meant to link https://github.com/microsoft/ebpf-for-windows/ instead (discussed on HN recently) which is an implementation by Microsoft using the above research project that indeed does not follow the suggestion from the authors of the research project to use validation and does require trusting user space.

Somewhat funnily, Microsoft also developed eBPF for Windows.

Not for long https://github.com/microsoft/ebpf-for-windows

The osdev wiki has an article explaining it. Mind you, ACPICA is quite heavy. If you don’t mind running into potential unsupported boards on real hardware (which should be quite rare and the developers will fix it if they can), you might want to look at LAI (https://github.com/managarm/lai). It works fine under QEMU so if you’re only doing virtualization there are no problems. LAI is a lot less convoluted to port, less code and less bloat. In essence, it’s add source files from LAI to your source tree, define and implement a few functions (last I checked less than 10 for basic operations if I recall correctly) and call like two LAI functions to enumerate namespaces and enable ACPI mode. LAI comes with documentation and there is a support channel on both discord and irc, linked in the readme of the repo.