From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57994) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V3BL6-0006Le-Q7 for qemu-devel@nongnu.org; Sat, 27 Jul 2013 16:43:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V3BL0-0005Yu-KU for qemu-devel@nongnu.org; Sat, 27 Jul 2013 16:43:44 -0400 Received: from cantor2.suse.de ([195.135.220.15]:44446 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V3BL0-0005Yo-AW for qemu-devel@nongnu.org; Sat, 27 Jul 2013 16:43:38 -0400 Message-ID: <51F430F4.6020708@suse.de> Date: Sat, 27 Jul 2013 22:43:32 +0200 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 References: <1374941897-11956-1-git-send-email-hpoussin@reactos.org> <51F4218A.1060802@weilnetz.de> In-Reply-To: <51F4218A.1060802@weilnetz.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH for-1.6] target-mips: do not raise exceptions when accessing invalid memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil , =?UTF-8?B?SGVydsOpIFBvdXNzaW5lYXU=?= Cc: Peter Maydell , qemu-devel@nongnu.org Am 27.07.2013 21:37, schrieb Stefan Weil: > Am 27.07.2013 19:43, schrieb Peter Maydell: >> On 27 July 2013 17:18, Herv=C3=A9 Poussineau wr= ote: >>> Another solution would be to add a big dummy memory regions on all MI= PS boards >>> to catch memory accesses and not raise an exception. However, this me= ans that >>> each MIPS board will have its own unassigned memory handler, differen= t from the >>> global QEMU one. >> Better would be to at least provide fake RAZ/WI implementations of >> devices for the boards, rather than making the dummy region cover >> the whole of the address space. Not 1.6 material, though. >=20 > I prefer keeping the correct code for target-mips/op_helper.c > and adding either the big dummy memory regions or fake > device implementations (both with TODO comments) for 1.6. The problem I see with that is, so far no one has stepped up with a list of what memory ranges / devices we are talking about. The simplest for 1.6 might be to re-add an #ifndef TARGET_MIPS around the refactored call to restore old behavior. Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC= rnberg