File 0017-linux-user-arm-no-tb_flush-on-reset.patch of Package qemu

Overview Repositories Revisions Requests Users Attributes Meta

File 0017-linux-user-arm-no-tb_flush-on-reset.patch of Package qemu (Revision f2e533db8a58604ac4af7bfd00d1285a)

Currently displaying revision f2e533db8a58604ac4af7bfd00d1285a , Show latest

From 1f7a819e8553dce0bf9c5ab6280b012483cd7b6d Mon Sep 17 00:00:00 2001
From: Alexander Graf <agraf@suse.de>
Date: Tue, 29 May 2012 15:30:01 +0200
Subject: [PATCH] linux-user: arm: no tb_flush on reset

When running automoc4 as linux-user guest program, it segfaults right after
it creates a thread. Bisecting pointed to commit a84fac1426 which introduces
tb_flush on reset.

So something in our thread creation is broken. But for now, let's revert the
change to at least get a working build again.
---
 target-arm/cpu.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/target-arm/cpu.c b/target-arm/cpu.c
index d40f2a7..3113456 100644
--- a/target-arm/cpu.c
+++ b/target-arm/cpu.c
@@ -133,7 +133,11 @@ static void arm_cpu_reset(CPUState *s)
      * bake assumptions about into translated code, so we need to
      * tb_flush().
      */
+#if !defined(CONFIG_USER_ONLY)
+    /* XXX hack alert! automoc4 segaults after spawning a new thread with this
+           flush enabled */
     tb_flush(env);
+#endif
 }
 
 #ifndef CONFIG_USER_ONLY

Places

File 0017-linux-user-arm-no-tb_flush-on-reset.patch of Package qemu (Revision f2e533db8a58604ac4af7bfd00d1285a)

Places