On Mon, Jan 23, 2023 at 04:51:16PM -0800, Ben Gardon wrote: > On Thu, Jan 12, 2023 at 7:50 PM Ricardo Koller <ricarkol@xxxxxxxxxx> wrote: > > > > Add a flag to kvm_pgtable_visit_ctx, KVM_PGTABLE_WALK_REMOVED, to > > indicate that the walk is on a removed table not accesible to the HW > > page-table walker. Then use it to avoid doing break-before-make or > > performing CMOs (Cache Maintenance Operations) when mapping a removed > > Nit: Should this say unmapping? Or are we actually going to use this > to map memory ? As you mentioned in the next commit, this will be clearer if I use "unliked" instead of "removed". Might end up rewriting this message as well, as I will be using Oliver's suggestion of using multiple flags, one for each operation to elide. > > > table. This is safe as these removed tables are not visible to the HW > > page-table walker. This will be used in a subsequent commit for > ...
