Re: [PATCH 2/2] KVM: x86: MMU: Move handle_mmio_page_fault() call to kvm_mmu_page_fault()

2016-02-22 Thread Paolo Bonzini
On 22/02/2016 09:23, Takuya Yoshikawa wrote: > Rather than placing a handle_mmio_page_fault() call in each > vcpu->arch.mmu.page_fault() handler, moving it up to > kvm_mmu_page_fault() makes the code better: > > - avoids code duplication > - for kvm_arch_async_page_ready(), which is the other

Re: [PATCH 2/2] KVM: x86: MMU: Move handle_mmio_page_fault() call to kvm_mmu_page_fault()

2016-02-22 Thread Paolo Bonzini
On 22/02/2016 09:23, Takuya Yoshikawa wrote: > Rather than placing a handle_mmio_page_fault() call in each > vcpu->arch.mmu.page_fault() handler, moving it up to > kvm_mmu_page_fault() makes the code better: > > - avoids code duplication > - for kvm_arch_async_page_ready(), which is the other

[PATCH 2/2] KVM: x86: MMU: Move handle_mmio_page_fault() call to kvm_mmu_page_fault()

2016-02-22 Thread Takuya Yoshikawa
Rather than placing a handle_mmio_page_fault() call in each vcpu->arch.mmu.page_fault() handler, moving it up to kvm_mmu_page_fault() makes the code better: - avoids code duplication - for kvm_arch_async_page_ready(), which is the other caller of vcpu->arch.mmu.page_fault(), removes an extra

[PATCH 2/2] KVM: x86: MMU: Move handle_mmio_page_fault() call to kvm_mmu_page_fault()

2016-02-22 Thread Takuya Yoshikawa
Rather than placing a handle_mmio_page_fault() call in each vcpu->arch.mmu.page_fault() handler, moving it up to kvm_mmu_page_fault() makes the code better: - avoids code duplication - for kvm_arch_async_page_ready(), which is the other caller of vcpu->arch.mmu.page_fault(), removes an extra