From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43130)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <B07421@freescale.com>) id 1Upkn5-00050K-Kj
	for qemu-devel@nongnu.org; Thu, 20 Jun 2013 15:45:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <B07421@freescale.com>) id 1Upkn2-0004FV-VU
	for qemu-devel@nongnu.org; Thu, 20 Jun 2013 15:45:07 -0400
Date: Thu, 20 Jun 2013 14:28:47 -0500
From: Scott Wood <scottwood@freescale.com>
In-Reply-To: <87ppvgbocw.fsf@codemonkey.ws> (from aliguori@us.ibm.com on Thu
	Jun 20 13:58:55 2013)
Message-ID: <1371756527.11064.14@snotra>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; delsp=Yes; format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 02/12] qtest: add spapr
 hypercall support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>, Paul Mackerras <paulus@samba.org>, Alexander Graf <agraf@suse.de>, Andreas =?iso-8859-1?q?F=E4rber?= <afaerber@suse.de>

On 06/20/2013 01:58:55 PM, Anthony Liguori wrote:
> Alexander Graf <agraf@suse.de> writes:
>=20
> > Am 20.06.2013 um 17:42 schrieb Anthony Liguori =20
> <aliguori@us.ibm.com>:
> >
> >> Andreas F=E4rber <afaerber@suse.de> writes:
> >>
> >>> The functions are called spapr_hcall*() but the protocol uses
> >>> papr_hypercall?
> >>
> >> The discrepancy is inherited in the KVM vs. QEMU interfaces.  It's
> >> called papr_hypercall in the KVM interface vs. spapr in QEMU.
> >>
> >> I honestly don't know what the distinction between spapr and papr =20
> is.
> >
> > PAPR is what PAPR calls itself. However, there is also an ePAPR for
> > BookE, so in order to distinguish the 2 more easily, we named the
> > server version spapr wherever we remembered to.
>=20
> So does it make sense to have papr_hypercall()?  Do hypercalls exist
> with the virtualization extensions on BookE?

Yes, there are hypercalls on booke.  Currently the few that KVM =20
supports are all handled in the kernel, but that may change, especially =20
since Alex is thinking about new hypercalls for guest reset/stop.

-Scott=