From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 3/5] KVM: PPC: Book3S HV: Handle memory slot deletion and modification correctly Date: Wed, 15 Aug 2012 12:23:19 +0300 Message-ID: <502B6A87.6010802@redhat.com> References: <20120806100207.GA8980@bloggs.ozlabs.ibm.com> <20120806100603.GD8980@bloggs.ozlabs.ibm.com> <20120809181612.GA12285@amt.cnet> <20120810003439.GB26420@bloggs.ozlabs.ibm.com> <20120810012532.GA15142@amt.cnet> <20120810110909.fd044ae1.yoshikawa.takuya@oss.ntt.co.jp> <20120810183553.GA16345@amt.cnet> <20120811003754.GA6016@bloggs.ozlabs.ibm.com> <20120813163411.GA22134@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Paul Mackerras , Gleb Natapov , Alex Williamson , Takuya Yoshikawa , Alexander Graf , kvm-ppc@vger.kernel.org, kvm@vger.kernel.org To: Marcelo Tosatti Return-path: In-Reply-To: <20120813163411.GA22134@amt.cnet> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/13/2012 07:34 PM, Marcelo Tosatti wrote: > > Avi, Gleb, Alex, do you know why it is necessary to support change of > GPA base again? BAR moving around. > Without taking into consideration backwards compatibility, userspace > can first delete the slot and later create a new one. Current qemu will in fact do that. Not sure about older ones. There is a difference in that the existing method is atomic. I don't see a real need for this atomicity though. -- error compiling committee.c: too many arguments to function