On Tue, Nov 30, 2021 at 05:10:53PM +0100, Jan Beulich wrote: > ept_free_entry() gets called after a flush - if one is necessary in the > first place - was already issued. That behavior is similar to NPT, which > also doesn't have any further flush in p2m_free_entry(). (Furthermore, > the function being recursive, in case of recursiveness way too many > flushes would have been issued.) > > Signed-off-by: Jan Beulich <[email protected]>
Reviewed-by: Roger Pau Monné <[email protected]> It's also worth noting that ept_free_entry doesn't modify the p2m itself - it gets handed an EPT entry to free, which should have been unhooked from the p2m previously by the caller, so it should be the responsibility of the caller to perform any flushes. Thanks, Roger.
