From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51000) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XijsN-0002QN-JV for qemu-devel@nongnu.org; Mon, 27 Oct 2014 08:58:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XijsH-0001rk-Eu for qemu-devel@nongnu.org; Mon, 27 Oct 2014 08:58:23 -0400 Received: from mnementh.archaic.org.uk ([2001:8b0:1d0::1]:54296) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XijsH-0001qz-8k for qemu-devel@nongnu.org; Mon, 27 Oct 2014 08:58:17 -0400 From: Peter Maydell Date: Mon, 27 Oct 2014 12:58:05 +0000 Message-Id: <1414414687-14265-1-git-send-email-peter.maydell@linaro.org> Subject: [Qemu-devel] [PATCH 0/2] target-arm: fix some exception-masking issues List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Sergey Fedorov , Greg Bellows , "Edgar E. Iglesias" , Fabian Aggeler , patches@linaro.org These patches fix a couple of issues I noticed with the existing code in the ARM arm_excp_unmasked() function while I was reviewing the TrustZone series: * we currently try to use the same function for M profile and A/R profile, which makes both code paths harder to read (and maybe one day we'll implement what M actually does, in which case the two code paths will be totally divergent...) * accidental || vs && confusion in the conditionals governing VIRQ and VFIQ I think they shouldn't conflict with the TZ patches except as minor textual conflicts. Peter Maydell (2): target-arm: Separate out M profile cpu_exec_interrupt handling target-arm: Correct condition for taking VIRQ and VFIQ target-arm/cpu.c | 49 +++++++++++++++++++++++++++++++++++++++---------- target-arm/cpu.h | 20 ++++---------------- 2 files changed, 43 insertions(+), 26 deletions(-) -- 1.9.1