From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Thu, 31 May 2012 03:22:24 +0000
Subject: Re: [PATCH] spapr: Add "memop" hypercall
Message-Id: <1338434544.16119.39.camel@pasglop>
List-Id: <kvm-ppc.vger.kernel.org>
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> <4FC35629.80704@redhat.com>
In-Reply-To: <4FC35629.80704@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org, kvm-ppc <kvm-ppc@vger.kernel.org>

On Mon, 2012-05-28 at 13:40 +0300, Avi Kivity wrote:
> 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.

At the moment SLOF just "uses it" when using the frame buffer. We could
advertise its presence via the device-tree, there's already stuff there
to expose what hypercalls or set of hypecalls are implemented for PAPR,
we could add qemu specific extensions.

Cheers,
Ben.