From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57509)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1bEdPn-0005MP-Ft
	for qemu-devel@nongnu.org; Sun, 19 Jun 2016 10:09:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1bEdPh-0000BT-FC
	for qemu-devel@nongnu.org; Sun, 19 Jun 2016 10:09:30 -0400
Message-ID: <1466345334.24271.123.camel@kernel.crashing.org>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Mon, 20 Jun 2016 00:08:54 +1000
In-Reply-To: <1ecfdda6-49a9-a737-80fd-a229c5a1fcf1@kaod.org>
References: <1465795496-15071-1-git-send-email-clg@kaod.org>
	<1465795496-15071-2-git-send-email-clg@kaod.org>
	<20160616010702.GI28087@voom.fritz.box>
	<20160617022731.GA19581@voom.fritz.box> <57639095.5010305@kaod.org>
	<576392B1.6030204@kaod.org> <5763A258.2010408@redhat.com>
	<5763D3EF.6060305@kaod.org> <5763D8D1.70701@redhat.com>
	<3258f4f3-6f5d-bb1f-9cac-2d19cac7ab53@kaod.org>
	<1466292910.24271.95.camel@kernel.crashing.org>
	<1ecfdda6-49a9-a737-80fd-a229c5a1fcf1@kaod.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 01/10] ppc: Fix
 rfi/rfid/hrfi/... emulation
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: =?ISO-8859-1?Q?C=E9dric?= Le Goater <clg@kaod.org>, Thomas Huth <thuth@redhat.com>, David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org

On Sun, 2016-06-19 at 14:49 +0200, C=C3=A9dric Le Goater wrote:
> > So my test is correct in the context of what we emulate today.
>=20
> OK. so this is an openbios issue when run under a ppc64. shouldn't we=C2=
=A0
> be using an openbios-ppc64 in that case ?=C2=A0=C2=A0
>=20
>=20
> We could be more strict with the rfi instruction.=C2=A0

Well, ppc64 isn't backward compatible with ppc32 at the supervisor
level, at least not on server chips (it is on bookE chips). So yes it's
an OpenBIOS problem but that doesn't mean we have to use openbios-ppc64=20
:-)=C2=A0

You can run a 32-bit OS or firmware on ppc64, but it needs to know that
it's running on a 64-bit chip and do a few things differently.

Cheers,
Ben.