[PATCH 2/3] kvm: rename last argument to kvm_get_dirty_log_protect

2018-11-28 Thread Paolo Bonzini
When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's pointer argument will always be false on exit, because no TLB flush is needed until the manual re-protection operation. Rename it from "is_dirty" to "flush", which more accurately tells the caller what they have to do

[PATCH 2/3] kvm: rename last argument to kvm_get_dirty_log_protect

2018-11-28 Thread Paolo Bonzini
When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's pointer argument will always be false on exit, because no TLB flush is needed until the manual re-protection operation. Rename it from "is_dirty" to "flush", which more accurately tells the caller what they have to do

Re: [PATCH 2/3] kvm: rename last argument to kvm_get_dirty_log_protect

2018-11-26 Thread Junaid Shahid
On 11/26/2018 08:54 AM, Paolo Bonzini wrote: > When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's > pointer argument will always be false on exit, because no TLB flush is needed > until the manual re-protection operation. Rename it from "is_dirty" to > "flush", >

Re: [PATCH 2/3] kvm: rename last argument to kvm_get_dirty_log_protect

2018-11-26 Thread Junaid Shahid
On 11/26/2018 08:54 AM, Paolo Bonzini wrote: > When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's > pointer argument will always be false on exit, because no TLB flush is needed > until the manual re-protection operation. Rename it from "is_dirty" to > "flush", >

[PATCH 2/3] kvm: rename last argument to kvm_get_dirty_log_protect

2018-11-26 Thread Paolo Bonzini
When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's pointer argument will always be false on exit, because no TLB flush is needed until the manual re-protection operation. Rename it from "is_dirty" to "flush", which more accurately tells the caller what they have to do

[PATCH 2/3] kvm: rename last argument to kvm_get_dirty_log_protect

2018-11-26 Thread Paolo Bonzini
When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's pointer argument will always be false on exit, because no TLB flush is needed until the manual re-protection operation. Rename it from "is_dirty" to "flush", which more accurately tells the caller what they have to do