vasilito 00da984779 kernel: consume LPIT MWAIT hint in idle_loop via AcpiVerb::SetLpiHint
- acpi.rs: LPI_MWAIT_HINT/LPI_MWAIT_HINT_SET atomics + set/get
  accessors; AcpiVerb::SetLpiHint handler reads the 4-byte LE
  payload and stores the firmware-recommended MWAIT hint.
- interrupt/mod.rs idle_loop(): prefer the LPIT entry_trigger hint
  (set by acpid) for mwait_loop(); fall back to CPUID leaf-5 max
  substate when no LPIT hint is available (no LPIT table, or
  pre-acpid boot).

This is the full Modern Standby integration: the CPU now enters the
firmware-optimal deepest LPI state during s2idle, not merely the
CPUID-reported deepest state.
2026-07-22 22:07:02 +09:00
2026-03-28 20:43:48 +01:00
2026-04-08 19:40:41 +01:00
2025-11-11 13:40:48 +00:00
2017-09-26 12:57:43 -06:00
2025-04-19 16:30:48 +02:00
2026-05-25 17:41:48 -06:00
2025-08-04 06:34:31 -06:00

Kernel

Redox OS Microkernel

docs SLOCs counter MIT licensed

Requirements

  • nasm needs to be available on the PATH at build time.

Building The Documentation

Use this command:

cargo doc --open --target x86_64-unknown-none

Debugging

QEMU

Running QEMU with the -s flag will set up QEMU to listen on port 1234 for a GDB client to connect to it. To debug the redox kernel run.

make qemu gdb=yes

This will start a virtual machine with and listen on port 1234 for a GDB or LLDB client.

GDB

If you are going to use GDB, run these commands to load debug symbols and connect to your running kernel:

(gdb) symbol-file build/kernel.sym
(gdb) target remote localhost:1234

LLDB

If you are going to use LLDB, run these commands to start debugging:

(lldb) target create -s build/kernel.sym build/kernel
(lldb) gdb-remote localhost:1234

After connecting to your kernel you can set some interesting breakpoints and continue the process. See your debuggers man page for more information on useful commands to run.

Notes

  • Always use foo.get(n) instead of foo[n] and try to cover for the possibility of Option::None. Doing the regular way may work fine for applications, but never in the kernel. No possible panics should ever exist in kernel space, because then the whole OS would just stop working.

  • If you receive a kernel panic in QEMU, use pkill qemu-system to kill the frozen QEMU process.

How To Contribute

To learn how to contribute to this system component you need to read the following document:

Development

To learn how to do development with this system component inside the Redox build system you need to read the Build System and Coding and Building pages.

How To Build

To build this system component you need to download the Redox build system, you can learn how to do it on the Building Redox page.

This is necessary because they only work with cross-compilation to a Redox virtual machine, but you can do some testing from Linux.

Funding - Unix-style Signals and Process Management

This project is funded through NGI Zero Core, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.

NLnet foundation logo NGI Zero Logo

S
Description
RedBear Operating System, based on RedoxOS. Licenced under MIT license.
https://redbearos.org
Readme MIT 18 GiB
Languages
C 37.5%
C++ 37.2%
JavaScript 6.7%
QML 3.4%
HTML 3.2%
Other 11.4%