From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56079) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgnsg-0003Jg-VM for qemu-devel@nongnu.org; Mon, 05 Sep 2016 02:59:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bgnsb-0002lX-2p for qemu-devel@nongnu.org; Mon, 05 Sep 2016 02:59:45 -0400 Message-ID: <1473058763.2313.40.camel@kernel.crashing.org> From: Benjamin Herrenschmidt Date: Mon, 05 Sep 2016 16:59:23 +1000 In-Reply-To: <20160905025835.GF2587@voom.fritz.box> References: <1472661255-20160-1-git-send-email-clg@kaod.org> <1472661255-20160-3-git-send-email-clg@kaod.org> <20160905025835.GF2587@voom.fritz.box> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2 2/7] ppc/pnv: add a PnvChip object List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson , =?ISO-8859-1?Q?C=E9dric?= Le Goater Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, Alexander Graf On Mon, 2016-09-05 at 12:58 +1000, David Gibson wrote: >=20 > With the new chip class per cpu class, does this chip_type field > serve > any purpose any more? >=20 > > +=C2=A0=C2=A0=C2=A0 k->chip_f000f =3D 0x120d304980000000ull; >=20 > A comment somewhere explaining what this cryptic value is would be > nice. It's snapshot from an actual chip ;-) Some of the fields we know about such as the actual chip "type" and DD version but some are obscure even to us :-) Cheers, Ben. `