docs(qemu):EmulatorHooks as the safe alternative for QEMUhooks

crates/libafl_qemu/src/emu/hooks.rs

@@ -164,6 +164,12 @@ impl<ET, I, S> Default for EmulatorHookCollection<ET, I, S> {
 }
 
 /// Hook collection,
+///
+/// `EmulatorHooks` provides the standard interface for registering QEMU-based
+/// instrumentation in `LibAFL` from a high-level perspective.
+///
+/// It integrates with emulator modules to ensure hooks are registered
+/// safely and at the correct time.
 #[derive(Debug)]
 pub struct EmulatorHooks<ET, I, S> {
     qemu_hooks: QemuHooks,

crates/libafl_qemu/src/qemu/hooks.rs

@@ -936,6 +936,12 @@ pub type CrashHookClosure<ET, I, S> = Box<dyn FnMut(Qemu, &mut EmulatorModules<E
 /// The thin wrapper around QEMU hooks.
 /// It is considered unsafe to use it directly.
 ///
+/// It is recommended to use [`crate::emu::EmulatorHooks`], which provides a safe, structured
+/// abstraction on top of [`QemuHooks`] and integrates with emulator modules.
+///
+/// Existing emulator modules (for example, syscall injection or coverage modules) provide concrete usage
+/// examples of registering hooks via [`crate::emu::EmulatorHooks`].
+///
 /// There are several types of hooks in place:
 ///
 /// • **Instruction** hooks: as the name suggests, to hook a specific