From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41125) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEw7o-0006jH-Q1 for qemu-devel@nongnu.org; Mon, 20 Jun 2016 06:08:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bEw7i-0007Zx-OU for qemu-devel@nongnu.org; Mon, 20 Jun 2016 06:08:11 -0400 Message-ID: <1466415136.24271.146.camel@kernel.crashing.org> From: Benjamin Herrenschmidt Date: Mon, 20 Jun 2016 19:32:16 +1000 In-Reply-To: <1466409752.24271.140.camel@kernel.crashing.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> <3B48DA40-D79B-416A-84E7-4743F60C2657@suse.de> <1466374521.24271.130.camel@kernel.crashing.org> <1466375718.24271.132.camel@kernel.crashing.org> <1466406504.24271.136.camel@kernel.crashing.org> <1466409752.24271.140.camel@kernel.crashing.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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?C=E9dric?= Le Goater , Alexander Graf Cc: Thomas Huth , David Gibson , qemu-ppc@nongnu.org, qemu-devel@nongnu.org On Mon, 2016-06-20 at 18:02 +1000, Benjamin Herrenschmidt wrote: > On Mon, 2016-06-20 at 17:08 +1000, Benjamin Herrenschmidt wrote: > > =C2=A0 > > That fixed, it dies elsewhere in something related to page faults, > > still digging. > > =C2=A0 > Next problem: Darwin kernel assumes DSISR is 0 on a 0x380 exception ! >=20 > qemu was leaving it to whatever value it had before. Kaboom. >=20 > Now it crashes a bit further :-) Right so it tries to load a MacRISC2 PE because we don't really emulate a MacRISC4 with U3 etc... and that isn't going to do it any good, really.. I'm not *actually* sure where MacOS gets itself into a spin, it seems to be poking at something at 0xf280_0000 which is somewhat odd as this would be the IO space and we have nothing there afaik, but I am not enough of a MacOS expert to figure out quite how to track down which kext it gets into etc... In any case, the machine we give it is definitely nowhere near a real G5 and that might be the main reason. More work needed. I'll still cleanup & submit my current crop of fixes in case somebody wants to have a look. Cheers, Ben.