From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53023) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHbOh-0005DO-5T for qemu-devel@nongnu.org; Sat, 31 Jan 2015 11:59:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YHbOd-00074Q-NE for qemu-devel@nongnu.org; Sat, 31 Jan 2015 11:59:50 -0500 Received: from mail-la0-f46.google.com ([209.85.215.46]:63842) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHbOd-00074G-GK for qemu-devel@nongnu.org; Sat, 31 Jan 2015 11:59:47 -0500 Received: by mail-la0-f46.google.com with SMTP id s18so29853571lam.5 for ; Sat, 31 Jan 2015 08:59:46 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Sat, 31 Jan 2015 16:59:25 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] debugging qemu arm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Attila Csosz Cc: QEMU Developers On 31 January 2015 at 16:50, Attila Csosz wrote: > Where is the arm-to-x86 call in QEMU code? Which tool/library call generates > this code? We generate the code in target-arm/translate.c (actually we generate a TCG intermediate representation which is subsequently turned into x86 instructions by the TCG backend in tcg/i386/). The main runtime loop is in exec.c: when we call tcg_qemu_tb_exec() this is actually a jump to generated code: # define tcg_qemu_tb_exec(env, tb_ptr) \ ((uintptr_t (*)(void *, void *))tcg_ctx.code_gen_prologue)(env, tb_ptr) -- PMM