From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH] kvm: Don't walk memory_size == 0 slots in kvm_client_migration_log Date: Thu, 15 Jul 2010 22:12:57 -0300 Message-ID: <20100716011257.GA21287@amt.cnet> References: <20100714193606.7124.80638.stgit@localhost6.localdomain6> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, avi@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35416 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935168Ab0GPCVf (ORCPT ); Thu, 15 Jul 2010 22:21:35 -0400 Content-Disposition: inline In-Reply-To: <20100714193606.7124.80638.stgit@localhost6.localdomain6> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Jul 14, 2010 at 01:36:49PM -0600, Alex Williamson wrote: > If we've unregistered a memory area, we should avoid calling > qemu_get_ram_ptr() on the left over phys_offset cruft in the > slot array. Now that we support removing ramblocks, the > phys_offset ram_addr_t can go away and cause a lookup fault > and abort. > > Signed-off-by: Alex Williamson Applied to uq/master branch, thanks.