From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53000) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjZqb-0002ah-46 for qemu-devel@nongnu.org; Fri, 14 Dec 2012 13:18:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TjZqY-0002Vq-Oa for qemu-devel@nongnu.org; Fri, 14 Dec 2012 13:18:57 -0500 Date: Fri, 14 Dec 2012 12:18:42 -0600 From: Scott Wood References: <1355451124-2559-1-git-send-email-scottwood@freescale.com> <1355451124-2559-5-git-send-email-scottwood@freescale.com> In-Reply-To: (from agraf@suse.de on Fri Dec 14 06:35:12 2012) Message-ID: <1355509122.4740.2@snotra> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 4/6] openpic: don't crash on a register access without a CPU context List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org On 12/14/2012 06:35:12 AM, Alexander Graf wrote: >=20 > On 14.12.2012, at 03:12, Scott Wood wrote: >=20 > > If we access a register via the QEMU memory inspection commands =20 > (e.g. > > "xp") rather than from guest code, we won't have a CPU context. > > Gracefully fail to access the register in that case, rather than > > crashing. >=20 > Can't we set cpu_single_env in the debug memory access case? I'm not =20 > sure this is the only device with that problem, and by always having =20 > cpu_single_env available we would completely get rid of the whole bug =20 > category. Which CPU would you pick? -Scott=