From 9980bbb9965ee2df42f94aafa817e91835dad406 Mon Sep 17 00:00:00 2001 From: Jack Veenstra Date: Tue, 5 May 2009 10:35:03 -0700 Subject: Add support for tracing Java method entry/exit to qemu. This is part of a larger change to add support for tracing Java methods. There is also a kernel change and a small change to the Dalvik interpreter that will be checked in separately. There used to be support for tracing Java methods but it relied on trapping every store and checking if the store address matched a special "magic" region (and that stopped working because we can no longer trap on loads and stores). The new approach uses a memory-mapped page to catch stores to just that page. --- trace.h | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'trace.h') diff --git a/trace.h b/trace.h index ebb0e8c..1134d06 100644 --- a/trace.h +++ b/trace.h @@ -20,16 +20,6 @@ extern uint64_t start_time, end_time; extern uint64_t elapsed_usecs; extern uint64 Now(); -// Define magic addresses so that the simulated program can interact with the -// simulator. -#define kMagicBaseAddr 0x08000000 -#define kMagicBaseMask 0xfffff000 -#define kMagicOffsetMask 0x00000fff - -#define kMethodTraceEnterOffset 0x0004 -#define kMethodTraceExitOffset 0x0008 -#define kMethodTraceExceptionOffset 0x000c - struct TranslationBlock; // For tracing dynamic execution of basic blocks -- cgit v1.1