Zach Reizner ce8961d1fc allow non-dirty log memory regions from the plugin process ... Dirty logging is not necessary for every memory region, so the plugin process should be able to specific exactly which regions it would like dirty logging enabled for. TEST=cargo test --features plugin BUG=chromium:800626 Change-Id: I28b8285357e7de1c8c3a1392bdfdb4853ec5a654 Reviewed-on: https://chromium-review.googlesource.com/900294 Commit-Ready: Zach Reizner <zachr@chromium.org> Tested-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>		2018-02-12 22:42:37 -08:00
..
mini_plugin_template.c	add support for accessing debug registers in the plugin process	2018-02-12 22:42:35 -08:00
plugin.policy
plugin_adder.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_dirty_log.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_ioevent.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_irqfd.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugins.rs	add plugin support for model specific registers	2018-02-12 22:42:36 -08:00