From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bomcf-0004V8-7E for qemu-devel@nongnu.org; Tue, 27 Sep 2016 03:16:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bomca-0007ll-W7 for qemu-devel@nongnu.org; Tue, 27 Sep 2016 03:16:12 -0400 Received: from 7.mo4.mail-out.ovh.net ([178.33.253.54]:47288) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bomca-0007ka-QG for qemu-devel@nongnu.org; Tue, 27 Sep 2016 03:16:08 -0400 Received: from player691.ha.ovh.net (b9.ovh.net [213.186.33.59]) by mo4.mail-out.ovh.net (Postfix) with ESMTP id E954F544F for ; Tue, 27 Sep 2016 09:16:07 +0200 (CEST) References: <1473943560-14846-1-git-send-email-clg@kaod.org> <1473943560-14846-8-git-send-email-clg@kaod.org> <20160921060845.GC20488@umbus> <20160923024654.GT2085@umbus.fritz.box> <20160927023548.GC15376@umbus.fritz.box> <1474956641.2857.277.camel@kernel.crashing.org> From: =?UTF-8?Q?C=c3=a9dric_Le_Goater?= Message-ID: Date: Tue, 27 Sep 2016 09:16:03 +0200 MIME-Version: 1.0 In-Reply-To: <1474956641.2857.277.camel@kernel.crashing.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v3 07/10] ppc/pnv: add XSCOM infrastructure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt , David Gibson Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org On 09/27/2016 08:10 AM, Benjamin Herrenschmidt wrote: > On Tue, 2016-09-27 at 07:54 +0200, C=C3=A9dric Le Goater wrote: >> >>> but I guess if you have the decoding of those "core" registers=20 >>> here as well, then that doesn't make so much sense. >=20 > Those core registers may well change with P9, we havne't looked closely > yet... Neither have I ... qemu/pnv reaches the kernel but this is really a=20 "Frankenstein P9". The interrupt controller is missing.=20 C.=20 >> yes and there is also the handling of the XSCOM failures. >> >> I can add some prologue handler to cover those "core" registers >> but adding a MemoryRegion, ops, init and mapping would be a lot=20 >> of churn just to return 0. >> >> Thanks,