Remove MM_MODE_NOINVALIDATE.
This flag exists to avoid paying the cost required for consistency when
consistency is not required. It was used for stage-2 allocation when the
VMs are initially being created i.e. there is a point before which all
stage-2 updates don't invalidate and after which they do. Given this, it
can move to the same approach used by the locks for dlog and mpool
allowing the mode clutter to be removed from where is doesn't belong.
Change-Id: I9be9e42c1daaf8570d7555bb3f37876aa7c3bd51
diff --git a/src/api.c b/src/api.c
index fa26e1d..e1d36ae 100644
--- a/src/api.c
+++ b/src/api.c
@@ -380,7 +380,7 @@
*/
fail_undo_all:
vm->mailbox.send = NULL;
- mm_unmap(pa_send_begin, pa_send_end, 0, &local_page_pool);
+ mm_unmap(pa_send_begin, pa_send_end, &local_page_pool);
fail_undo_send_and_recv:
mm_vm_identity_map(&vm->ptable, pa_recv_begin, pa_recv_end,