From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44821) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewZhw-0001GE-JI for qemu-devel@nongnu.org; Thu, 15 Mar 2018 16:42:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ewZhv-0002bH-TN for qemu-devel@nongnu.org; Thu, 15 Mar 2018 16:42:40 -0400 Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]:44808) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ewZhv-0002aN-NO for qemu-devel@nongnu.org; Thu, 15 Mar 2018 16:42:39 -0400 Received: by mail-oi0-x233.google.com with SMTP id b8so6853197oib.11 for ; Thu, 15 Mar 2018 13:42:39 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Thu, 15 Mar 2018 20:42:18 +0000 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] ARM64 Interrupt handling on QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brijen Raval Cc: QEMU Developers On 15 March 2018 at 20:24, Brijen Raval wrote: > On Thu, Mar 15, 2018 at 2:59 AM Peter Maydell > wrote: >> Exception 5 is IRQ. (These numbers are all internal to QEMU, and >> don't have any architectural or guest-visible relevance. They're >> the EXCP_* constants defined at the top of target/arm/cpu.h.) > > > Yup I checked out the QEMU source and confirmed above. So is there any way > to find out what is the IRQ for? You would need to look at what the state of the interrupt controller is. You can turn on all the tracepoints in the GIC with -d trace:gic* (though to understand what it's saying you may need to have some familiarity with the GIC spec and/or look at the code). thanks -- PMM