On Tue, Oct 08, 2024 at 07:24:01PM +0000, Kaplan, David wrote: > > There are currently 4 mitigations that use VERW to flush different cpu buffers. This > > can cause confusion when trying to disable all the different VERW mitigations. > > Simplify enabling/disabling these mitigations by creating a single parameter for > > controlling them. > > Just curious, what is the use case for disabling the different VERW > mitigations (but not other mitigations)? Is that a testing/debugging > use case or a production use case? I'm also wondering about this. I like the idea of cleaning up the code mess (like in patch 6) but I'm not sure I see the benefit of this patch to add yet another option. Is this a realistic use case? Are people really going to want to enable/disable VERW mitigations as a group? -- Josh
