search for: remove_write_access

Just found this patch in house which I thought sent out already. :-) Still one thing remaining is to special case for UP guest which suffers overhead from this change... ---- Remove lock on first guest table walk Existing shadow fault path grabs big lock before walking guest tables, to ensure consistency with shadow content lest concurrent change from other vcpu in a bad OS. But this lock

..., the guest_map_l1e and guest_get_eff_l1e functions can be >allowed to >drop the shadow lock and call guest_walk_tables with shadow_op == 0. >That would mean that there are no callers left setting shadow_op to 1, >and then the shadow_op argument (and the whole mechanism for calling >remove_write_access from guest_walk_tables) could be removed. Thanks for clarification. > >I think that in guest_walk_tables, you need to add an rmb() after >reading the version number to stop the compiler from hoisting the >pagetable reads to before the version read. Yes, my overlook and thanks for poi...