Mathieu Tarral

I should cc @bamiaux on this discussion :)

I'm also wondering how we could push the `Read` trait further into the user API ? Afterall, we should reuse a maximum of rust traits, and avoiding inventing unecessary APIs....

Design in progress here: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=129baa6895e5f0a1e65415eb9b94fd02 One thing I learned: we don't need 2 methods `memory()` and `padded_memory()`. The [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) trait has a [`read_exact()`](https://doc.rust-lang.org/std/io/trait.Read.html#method.read_exact) function that can be reimplemented, and used...

I was looking at adding a new function in the `Introspectable` trait: ~~~Rust fn detect() -> Result where Self: Sized { ~~~ And then you could loop over the `DriverType`...

We should rename this feature as hypervisor test, and test whether a given domain name is available on for a specific hypervisor. Implementing the same logic that LibVMI's [`driver_init_mode`](https://github.com/libvmi/libvmi/blob/master/libvmi/driver/driver_interface.c#L50) function...

Next here would be to enable a set of features by default. Of course, we have to take the platform into account, Linux or Windows. I tried to play with...

Thanks for finding this. At least this should be available in nightly already, according to: > Target-specific features for dependencies has been implemented and is available as a nightly-only feature...

Related: https://github.com/libvmi/libvmi/blob/master/libvmi/driver/xen/xen_events.c#L3213

Documentation: - https://os.phil-opp.com/paging-implementation/ - https://osblog.stephenmarz.com/ch3.html Also, it looks like this feature has already been implemented in [`kvmi-semantic`](https://github.com/kylerky/kvmi-rs/tree/master/kvmi-semantic) crate: https://github.com/kylerky/kvmi-rs/blob/master/kvmi-semantic/src/memory/address_space.rs#L210 cc @kylerky can you tell us more about the state virtual...

@arnabcs17b006 same question here ?