From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40758) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5Wwq-00042X-IS for Qemu-devel@nongnu.org; Thu, 18 Jun 2015 06:21:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5Wwn-0006Wf-D7 for Qemu-devel@nongnu.org; Thu, 18 Jun 2015 06:21:28 -0400 Received: from mail-yk0-f179.google.com ([209.85.160.179]:35396) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5Wwn-0006WH-9c for Qemu-devel@nongnu.org; Thu, 18 Jun 2015 06:21:25 -0400 Received: by ykar6 with SMTP id r6so62226684yka.2 for ; Thu, 18 Jun 2015 03:21:24 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <5915E793-8982-4B5E-84C3-3565ACBF91A9@livius.net> References: <5915E793-8982-4B5E-84C3-3565ACBF91A9@livius.net> From: Peter Maydell Date: Thu, 18 Jun 2015 11:21:04 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] How to trigger faults for missing peripherals? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liviu Ionescu Cc: QEMU Developers On 18 June 2015 at 10:45, Liviu Ionescu wrote: > In order to make the Cortex-M emulation accurate, I would need to configure the missing address ranges to trigger memory faults. > > I noticed that the emulator defines a memory range to > cover the entire 64-bits memory space. Is it possible > to make it trigger exceptions? In theory, but the machinery to do this is a bit broken and there's a bunch of cleanup and design fixes necessary before we can turn it on for ARM. "do_unassigned_access" is the QOM CPUClass hook for this, and searching the mailing list archives will probably turn up discussion about the fixes needed. -- PMM