From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] spapr: Add "memop" hypercall Date: Mon, 21 May 2012 16:55:08 +0300 Message-ID: <4FBA493C.1000308@redhat.com> References: <1337585042.2779.4.camel@pasglop> <4FBA0F23.5040601@redhat.com> <1337594641.2779.59.camel@pasglop> <4FBA13DF.7040009@redhat.com> <1337600909.2779.93.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Alexander Graf , kvm@vger.kernel.org, kvm-ppc To: Benjamin Herrenschmidt Return-path: In-Reply-To: <1337600909.2779.93.camel@pasglop> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/21/2012 02:48 PM, Benjamin Herrenschmidt wrote: > On Mon, 2012-05-21 at 13:07 +0300, Avi Kivity wrote: > > > Now I'm adding another one, so yes, it's looking like a trend :-) I'll > > > look into it, at this stage with only those two, adding some comments in > > > the header might be plenty enough. > > > > Documentation/virtual/kvm/ppc-pv.txt is a nice central place for these. > > It would be even better if you could add them to the spec. > > They don't quite fit with the other PV calls in there which use a > different HV calling mechanism alltogether, but I can certainly add a > specific section. > > As to adding things to PAPR, let's assume for now that this isn't > possible :-) Besides, those two hypercalls are pretty specific to the > way things are implemented in qemu and are in both case more or less > private mechanisms used to communicate between qemu and the SLOF > firmware we run in inside qemu, they aren't really used by random guest > SW and aren't meant to be. Okay. But let's have a spec, even a kvm-private one, and then an implementation of that spec, instead of an implementation and some documentation added as an afterthought (or not). > It's a bit like if you had private calls between seabios and qemu... We document those too. -- error compiling committee.c: too many arguments to function