On 03/01/2012 12:32 PM, Takuya Yoshikawa wrote: > Dropped such mappings when we enabled dirty logging and we will never > create new ones until we stop the logging. > > For this we introduce a new function which can be used to write protect > a range of PT level pages: although we do not need to care about a range > of pages at this point, the following patch will need this feature to > optimize the write protection of many pages. > > It occurs to me that we should write-protect huge page tables, since it makes write protection much faster (we make up for this later at write fault time, but that might not occur, and even if it does we reduce guest jitter). In fact I once proposed a more involved variant, called O(1) write protection, in which we write-protect the topmost page table only and only un-write-protect the paths that fault. That can be done later however and shouldn't affect this patchset. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
