From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benjamin Herrenschmidt <benh@au1.ibm.com>
Date: Fri, 04 Sep 2015 10:40:04 +0000
Subject: Re: [Qemu-ppc] KVM memory slots limit on powerpc
Message-Id: <1441363204.2929.37.camel@au1.ibm.com>
List-Id: <kvm-ppc.vger.kernel.org>
References: <55E965FC.8080909@redhat.com> <55E96B87.8020900@de.ibm.com>
	 <55E96CB9.4070100@suse.de> <55E96D6B.2070201@de.ibm.com>
	 <55E97264.6090602@redhat.com>
In-Reply-To: <55E97264.6090602@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Thomas Huth <thuth@redhat.com>, Christian Borntraeger <borntraeger@de.ibm.com>, Alexander Graf <agraf@suse.de>, kvm-ppc@vger.kernel.org, qemu-ppc@nongnu.org, kvm@vger.kernel.org
Cc: David Gibson <dgibson@redhat.com>, Alex Williamson <alex.williamson@redhat.com>, Bharata B Rao <bharata@linux.vnet.ibm.com>

On Fri, 2015-09-04 at 12:28 +0200, Thomas Huth wrote:

> > Maybe some rcu protected scheme that doubles the amount of memslots
> > for
> > each overrun? Yes, that would be good and even reduce the footprint
> > for
> > systems with only a small number of memslots.
> 
> Seems like Alex Williamson already posted a patchset for growable
> memslots a couple of years ago:
> 
>  http://www.spinics.net/lists/kvm/msg50491.html
> 
> But I didn't quite spot the result in that thread why it never has 
> been
> included upstream. Alex (W.), do you remember the outcome?

Isn't the memslot array *already* protected by RCU anyway ?

Cheers,
Ben.