Hi, Yesterday, I tried to read mmu code but soon came back to dirty logging! -- My brain's tlb flush seems to have a serious bug!
Soon after that, I reached to this patch set. What I thought was that I might be able to improve KVM's interactivity in the future if I can suppress write protection for hot frame buffer regions by using hint from user land: This may help us solve the interactivity problems on the TODO lists in KVM wiki. - Just scaling up frame rate will soon suffer from many page faults. - Scaling down may result in bad response. For live-migration, it may be possible to do fine grained get dirty log. I want to know about this patch's relationship with your O(1) write protection plan. Is it possible to co-exist? If so, I will do some performance test. - I'm not sure in which conditions this hack has advantages yet. Any comments will be appriciated! Takuya -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
