From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50623) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZDC6a-0006eb-4g for qemu-devel@nongnu.org; Thu, 09 Jul 2015 09:43:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZDC6V-00037t-4m for qemu-devel@nongnu.org; Thu, 09 Jul 2015 09:43:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54001) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZDC6U-00037j-Vo for qemu-devel@nongnu.org; Thu, 09 Jul 2015 09:43:07 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 805782C7700 for ; Thu, 9 Jul 2015 13:43:06 +0000 (UTC) References: <1436442444-132020-1-git-send-email-imammedo@redhat.com> <1436442444-132020-5-git-send-email-imammedo@redhat.com> <20150709155919-mutt-send-email-mst@redhat.com> From: Paolo Bonzini Message-ID: <559E7A65.6080908@redhat.com> Date: Thu, 9 Jul 2015 15:43:01 +0200 MIME-Version: 1.0 In-Reply-To: <20150709155919-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 4/7] pc: fix QEMU crashing when more than ~50 memory hotplugged List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" , Igor Mammedov Cc: qemu-devel@nongnu.org On 09/07/2015 15:06, Michael S. Tsirkin wrote: > > QEMU asserts in vhost due to hitting vhost backend limit > > on number of supported memory regions. > > > > Describe all hotplugged memory as one continuos range > > to vhost with linear 1:1 HVA->GPA mapping in backend. > > > > Signed-off-by: Igor Mammedov > > Hmm - a bunch of work here to recombine MRs that memory listener > interface breaks up. In particular KVM could benefit from this too (on > workloads that change the table a lot). Can't we teach memory core to > pass hva range as a single continuous range to memory listeners? Memory listeners are based on memory regions, not HVA ranges. Paolo