From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=57716 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q6oet-00017Y-EJ for qemu-devel@nongnu.org; Mon, 04 Apr 2011 14:37:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q6oes-0006eN-9c for qemu-devel@nongnu.org; Mon, 04 Apr 2011 14:37:51 -0400 Received: from mail-vx0-f173.google.com ([209.85.220.173]:65152) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q6oes-0006dt-3a for qemu-devel@nongnu.org; Mon, 04 Apr 2011 14:37:50 -0400 Received: by vxb41 with SMTP id 41so5046749vxb.4 for ; Mon, 04 Apr 2011 11:37:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20100522104440.18257.92813.stgit@skyserv> <20100522105234.18257.53650.stgit@skyserv> From: Blue Swirl Date: Mon, 4 Apr 2011 21:37:28 +0300 Message-ID: Subject: Re: [Qemu-devel] [PATCH 4/5] sparc64: fix mmu context at trap levels above zero Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Artyom Tarasenko Cc: qemu-devel@nongnu.org On Mon, Apr 4, 2011 at 8:25 PM, Artyom Tarasenko wrot= e: > On Sat, May 22, 2010 at 12:52 PM, Igor V. Kovalenko > wrote: >> --- a/target-sparc/helper.c >> +++ b/target-sparc/helper.c >> @@ -572,6 +572,23 @@ static int get_physical_address(CPUState *env, targ= et_phys_addr_t *physical, >> =C2=A0 =C2=A0 /* ??? We treat everything as a small page, then explicitl= y flush >> =C2=A0 =C2=A0 =C2=A0 =C2=A0everything when an entry is evicted. =C2=A0*/ >> =C2=A0 =C2=A0 *page_size =3D TARGET_PAGE_SIZE; >> + >> +#if defined (DEBUG_MMU) >> + =C2=A0 =C2=A0/* safety net to catch wrong softmmu index use from dynam= ic code */ > > What does "wrong softmmu index" mean? Is it an error or an indication > that something is not implemented? > I'm hitting this net with the following message: The warning is not correct for CPUs without hypervisor mode. On T1/T2, the default access mode when TL > 1 is hypervisor or nucleus mode. Even then, the hypervisor could perform some accesses with kernel or user ASIs.