From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH 0/2] Expose available KVM free memory slot count to help avoid aborts Date: Tue, 25 Jan 2011 12:23:01 +0200 Message-ID: <4D3EA485.8030806@redhat.com> References: <20110121233040.22262.68117.stgit@s20.home> <20110124093241.GA28654@amt.cnet> <4D3D89B1.30300@siemens.com> <1295883899.3230.9.camel@x201> <1295933876.3230.46.camel@x201> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Marcelo Tosatti , "kvm@vger.kernel.org" , "ddutile@redhat.com" , "mst@redhat.com" , "chrisw@redhat.com" To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38968 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753395Ab1AYKXH (ORCPT ); Tue, 25 Jan 2011 05:23:07 -0500 In-Reply-To: <1295933876.3230.46.camel@x201> Sender: kvm-owner@vger.kernel.org List-ID: On 01/25/2011 07:37 AM, Alex Williamson wrote: > On Mon, 2011-01-24 at 08:44 -0700, Alex Williamson wrote: > > I'll look at how we might be > > able to allocate slots on demand. Thanks, > > Here's a first cut just to see if this looks agreeable. This allows the > slot array to grow on demand. This works with current userspace, as > well as userspace trivially modified to double KVMState.slots and > hotplugging enough pci-assign devices to exceed the previous limit (w/& > w/o ept). Hopefully I got the rcu bits correct. Does this look like > the right path? This can be trivially exhausted to pin all RAM. -- error compiling committee.c: too many arguments to function