From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57097) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4eOI-0005gD-PT for qemu-devel@nongnu.org; Wed, 09 Nov 2016 20:42:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4eOF-00053P-Kf for qemu-devel@nongnu.org; Wed, 09 Nov 2016 20:42:58 -0500 From: Balbir Singh Message-ID: Date: Thu, 10 Nov 2016 12:42:37 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [TRIVIAL][RFC][PATCH] FU exceptions should carry a cause (IC) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-ppc@nongnu.org Cc: David Gibson , Cedric Le Goater , qemu-devel@nongnu.org As per the ISA we need a cause for FU exceptions.Executing a tabort r9 for example in libc, causes a EXCP_FU exception. We don't wire up the IC (cause) when we post the exception. The cause is required for the kernel to do the right thing. I caught this issue while testing the latest kernel against Cedrics' latest pnv ipmi branch. Signed-off-by: Balbir singh --- target-ppc/excp_helper.c | 1 + 1 file changed, 1 insertion(+) diff --git a/target-ppc/excp_helper.c b/target-ppc/excp_helper.c index 808760b..cccea8d 100644 --- a/target-ppc/excp_helper.c +++ b/target-ppc/excp_helper.c @@ -427,6 +427,7 @@ static inline void powerpc_excp(PowerPCCPU *cpu, int excp_model, int excp) case POWERPC_EXCP_VPU: /* Vector unavailable exception */ case POWERPC_EXCP_VSXU: /* VSX unavailable exception */ case POWERPC_EXCP_FU: /* Facility unavailable exception */ + env->spr[SPR_FSCR] |= ((target_ulong)env->error_code << 56); break; case POWERPC_EXCP_PIT: /* Programmable interval timer interrupt */ LOG_EXCP("PIT exception\n"); -- 2.9.3