From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41644) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTujU-0004VO-H1 for qemu-devel@nongnu.org; Fri, 06 Mar 2015 11:04:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YTujQ-0004Ws-8b for qemu-devel@nongnu.org; Fri, 06 Mar 2015 11:04:12 -0500 Message-ID: <54F9CFF5.4070800@suse.de> Date: Fri, 06 Mar 2015 17:04:05 +0100 From: Alexander Graf MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] mfocrf missing on e500v2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Henderson Cc: qemu-ppc , qemu-devel Hi Richard, I've finally managed to check out why my e500v2 automated tests fail to run. Apparently they break because autotest wants to execute target code and runs into an illegal instruction while doing that: Program received signal SIGILL, Illegal instruction. 0xb57c84cc in ?? () (gdb) x /i $pc =3D> 0xb57c84cc: mfocrf r0,1 And lo and behold, I really couldn't find any reference to mfocrf in the e500v2 spec. Is there any way to disable setcond2 for those chips? Alex