Re: [PATCH v2 20/27] plugins: create CPUPluginState and migrate plugin_mask

On 2/23/24 8:21 PM, Alex Bennée wrote: We are going to want to keep track of some per-vCPU data for plugins and the logical place to do so is in track it in CPUState. For now this just moves the plugin_mask (renamed to event_mask) as the memory callbacks are accessed directly by TCG generated

[PATCH v2 20/27] plugins: create CPUPluginState and migrate plugin_mask

We are going to want to keep track of some per-vCPU data for plugins and the logical place to do so is in track it in CPUState. For now this just moves the plugin_mask (renamed to event_mask) as the memory callbacks are accessed directly by TCG generated code. Signed-off-by: Alex Bennée ---