Struct MemoryController

pub struct MemoryController<Driver>
where
    Driver: VmiDriver,
{ /* private fields */ }

Implements “memory breakpoints” by manipulating memory access permissions rather than modifying instructions.

When a breakpoint is inserted, the page is marked as non-executable - the guest can read or write to the page but cannot execute code from it without triggering an exception.

When a VCPU tries to execute code from the protected page, a VmiEvent is generated with a memory access reason. As with the BreakpointController, you can check if the event came from a breakpoint manager using BreakpointManager::contains_by_event or BreakpointManager::get_by_event.

Regular read and write operations proceed normally without generating events.

Trait Implementations

impl<Driver> TapController for MemoryController<Driver>

where Driver: VmiDriver,

type Driver = Driver

VMI driver type.

fn new() -> Self

Creates a new TapController.

fn check_event( &self, event: &VmiEvent<Driver::Architecture>, ) -> Option<(View, Gfn)>

Checks if the given event was caused by a breakpoint.

fn insert_breakpoint( &mut self, _vmi: &VmiCore<Driver>, _pa: Pa, _view: View, ) -> Result<(), VmiError>

Inserts a breakpoint at the given physical address.

fn remove_breakpoint( &mut self, _vmi: &VmiCore<Driver>, _pa: Pa, _view: View, ) -> Result<(), VmiError>

Removes a breakpoint at the given physical address.

fn monitor( &mut self, vmi: &VmiCore<Driver>, gfn: Gfn, view: View, ) -> Result<(), VmiError>

Monitors the given guest frame number.

fn unmonitor( &mut self, vmi: &VmiCore<Driver>, gfn: Gfn, view: View, ) -> Result<(), VmiError>

Unmonitors the given guest frame number.