Re: [PATCH v9 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled

Hi Peter, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on vhost/linux-next] [also build test WARNING on linus/master v5.7-rc7] [cannot apply to kvm/linux-next tip/auto-latest linux/master next-20200526] [if your patch is applied to the wrong git tree, please

Re: [PATCH v9 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled

Hi Peter, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on vhost/linux-next] [also build test WARNING on linus/master v5.7-rc7] [cannot apply to kvm/linux-next tip/auto-latest linux/master next-20200526] [if your patch is applied to the wrong git tree, please

Re: [PATCH v9 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled

On Tue, May 26, 2020 at 11:05:47PM +0800, kbuild test robot wrote: > >> arch/x86/kvm/mmu/mmu.c:1280:3: warning: Returning an integer in a function > >> with pointer return type is not portable. [CastIntegerToAddressAtReturn] > return false; > ^ A rebase accident for quite a few

Re: [PATCH v9 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled

Hi Peter, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on vhost/linux-next] [also build test WARNING on linus/master v5.7-rc7] [cannot apply to kvm/linux-next tip/auto-latest linux/master next-20200522] [if your patch is applied to the wrong git tree, please

[PATCH v9 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled

Because kvm dirty rings and kvm dirty log is used in an exclusive way, Let's avoid creating the dirty_bitmap when kvm dirty ring is enabled. At the meantime, since the dirty_bitmap will be conditionally created now, we can't use it as a sign of "whether this memory slot enabled dirty tracking".