From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] spapr: Add "memop" hypercall Date: Mon, 28 May 2012 13:40:41 +0300 Message-ID: <4FC35629.80704@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> <4FBA493C.1000308@redhat.com> <1337915561.16119.9.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: <1337915561.16119.9.camel@pasglop> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/25/2012 06:12 AM, Benjamin Herrenschmidt wrote: > > BTW. This is a qemu patch, and that hypercall isn't KVM related at all, > ie, it's implemented in qemu and is used with or without KVM, so > documenting it in the kernel tree makes little sense. Same goes with > H_RTAS. > > I'll add a doc to qemu in my next spin of it. > Depends. How do you detect it exists? Are you detecting kvm, or qemu, or the hypercall itself? I'd hate us to find ourselves in a maze of disconnected documentation with no clear guidelines on when a feature is available and when it is not. -- error compiling committee.c: too many arguments to function