From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52624) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bketB-0004T0-7M for qemu-devel@nongnu.org; Thu, 15 Sep 2016 18:12:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bket7-0002mG-42 for qemu-devel@nongnu.org; Thu, 15 Sep 2016 18:12:13 -0400 Message-ID: <1473977505.8689.371.camel@kernel.crashing.org> From: Benjamin Herrenschmidt Date: Fri, 16 Sep 2016 08:11:45 +1000 In-Reply-To: <1473943560-14846-8-git-send-email-clg@kaod.org> References: <1473943560-14846-1-git-send-email-clg@kaod.org> <1473943560-14846-8-git-send-email-clg@kaod.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 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: =?ISO-8859-1?Q?C=E9dric?= Le Goater , qemu-ppc@nongnu.org Cc: David Gibson , qemu-devel@nongnu.org On Thu, 2016-09-15 at 14:45 +0200, C=C3=A9dric Le Goater wrote: > =C2=A0- The PCB translation is too much of a constraint for a specific > =C2=A0=C2=A0 XSCOM address space, unless someone can explain me how to = address 8 > =C2=A0=C2=A0 bytes at 0xb0021 and another 8 different bytes at 0xb0022.= I don't > =C2=A0=C2=A0 think the address space and the memory regions were design= ed with > =C2=A0=C2=A0 this in mind. Please advise ! I'd say just dispatch pcb_addr << 3 to the memory regions (which is also the P9 translation iirc). Just add a quirk to the ADU/XSCOM dispatch object to do the additional unmangling needed on P7/P8 Cheers, Ben.