From 5146a69835bc9ba37fba7d3b0ff72ecaf9b98b74 Mon Sep 17 00:00:00 2001 From: Ali Saidi Date: Mon, 7 Jan 2013 13:05:33 -0500 Subject: cpu: rename the misleading inSyscall to noSquashFromTC isSyscall was originally created because during handling of a syscall in SE mode the threadcontext had to be updated. However, in many places this is used in FS mode (e.g. fault handlers) and the name doesn't make much sense. The boolean actually stops gem5 from squashing speculative and non-committed state when a write to a threadcontext happens, so re-name the variable to something more appropriate --- src/cpu/inorder/thread_context.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/cpu/inorder/thread_context.cc') diff --git a/src/cpu/inorder/thread_context.cc b/src/cpu/inorder/thread_context.cc index 16ffd5b0f..b8662ef4c 100644 --- a/src/cpu/inorder/thread_context.cc +++ b/src/cpu/inorder/thread_context.cc @@ -90,10 +90,10 @@ InOrderThreadContext::takeOverFrom(ThreadContext *old_context) copyArchRegs(old_context); thread->funcExeInst = old_context->readFuncExeInst(); - + old_context->setStatus(ThreadContext::Halted); - thread->inSyscall = false; + thread->noSquashFromTC = false; thread->trapPending = false; } @@ -159,7 +159,7 @@ InOrderThreadContext::serialize(std::ostream &os) void InOrderThreadContext::unserialize(Checkpoint *cp, const std::string §ion) { - panic("unserialize unimplemented"); + panic("unserialize unimplemented"); } -- cgit v1.2.3