2009-02-11 00:49:29 +01:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2007 MIPS Technologies, Inc.
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions are
|
|
|
|
* met: redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer;
|
|
|
|
* redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution;
|
|
|
|
* neither the name of the copyright holders nor the names of its
|
|
|
|
* contributors may be used to endorse or promote products derived from
|
|
|
|
* this software without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
|
|
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
* OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
|
|
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*
|
|
|
|
* Authors: Korey Sewell
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __CPU_INORDER_THREAD_CONTEXT_HH__
|
|
|
|
#define __CPU_INORDER_THREAD_CONTEXT_HH__
|
|
|
|
|
2009-09-23 17:34:21 +02:00
|
|
|
#include "config/the_isa.hh"
|
2009-02-11 00:49:29 +01:00
|
|
|
#include "cpu/exetrace.hh"
|
|
|
|
#include "cpu/thread_context.hh"
|
|
|
|
#include "cpu/inorder/thread_state.hh"
|
|
|
|
#include "cpu/inorder/cpu.hh"
|
|
|
|
|
|
|
|
class TranslatingPort;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Derived ThreadContext class for use with the InOrderCPU. It
|
|
|
|
* provides the interface for any external objects to access a
|
|
|
|
* single thread's state and some general CPU state. Any time
|
|
|
|
* external objects try to update state through this interface,
|
|
|
|
* the CPU will create an event to squash all in-flight
|
|
|
|
* instructions in order to ensure state is maintained correctly.
|
|
|
|
* It must be defined specifically for the InOrderCPU because
|
|
|
|
* not all architectural state is located within the O3ThreadState
|
|
|
|
* (such as the commit PC, and registers), and specific actions
|
|
|
|
* must be taken when using this interface (such as squashing all
|
|
|
|
* in-flight instructions when doing a write to this interface).
|
|
|
|
*/
|
|
|
|
class InOrderThreadContext : public ThreadContext
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
InOrderThreadContext() { }
|
|
|
|
|
2009-05-12 21:01:13 +02:00
|
|
|
/** Pointer to the CPU. */
|
2009-02-11 00:49:29 +01:00
|
|
|
InOrderCPU *cpu;
|
|
|
|
|
|
|
|
/** Pointer to the thread state that this TC corrseponds to. */
|
|
|
|
InOrderThreadState *thread;
|
|
|
|
|
|
|
|
/** Returns a pointer to the ITB. */
|
2009-05-12 21:01:13 +02:00
|
|
|
/** @TODO: PERF: Should we bind this to a pointer in constructor? */
|
|
|
|
TheISA::TLB *getITBPtr() { return cpu->getITBPtr(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Returns a pointer to the DTB. */
|
2009-05-12 21:01:13 +02:00
|
|
|
/** @TODO: PERF: Should we bind this to a pointer in constructor? */
|
|
|
|
TheISA::TLB *getDTBPtr() { return cpu->getDTBPtr(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
System *getSystemPtr() { return cpu->system; }
|
|
|
|
|
|
|
|
/** Returns a pointer to this CPU. */
|
2010-06-24 21:34:19 +02:00
|
|
|
BaseCPU *getCpuPtr() { return cpu; }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Returns a pointer to this CPU. */
|
2010-06-24 21:34:19 +02:00
|
|
|
std::string getCpuName() { return cpu->name(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Reads this CPU's ID. */
|
2010-06-24 21:34:19 +02:00
|
|
|
int cpuId() { return cpu->cpuId(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
int contextId() { return thread->contextId(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void setContextId(int id) { thread->setContextId(id); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Returns this thread's ID number. */
|
2010-06-24 21:34:19 +02:00
|
|
|
int threadId() { return thread->threadId(); }
|
|
|
|
void setThreadId(int id) { return thread->setThreadId(id); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
uint64_t readMicroPC()
|
2009-02-11 00:49:29 +01:00
|
|
|
{ return 0; }
|
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void setMicroPC(uint64_t val) { };
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
uint64_t readNextMicroPC()
|
2009-02-11 00:49:29 +01:00
|
|
|
{ return 0; }
|
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void setNextMicroPC(uint64_t val) { };
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2009-09-15 07:44:48 +02:00
|
|
|
#if FULL_SYSTEM
|
|
|
|
/** Returns a pointer to physical memory. */
|
2010-06-24 21:34:19 +02:00
|
|
|
PhysicalMemory *getPhysMemPtr()
|
2009-09-15 07:44:48 +02:00
|
|
|
{ assert(0); return 0; /*return cpu->physmem;*/ }
|
|
|
|
|
|
|
|
/** Returns a pointer to this thread's kernel statistics. */
|
2010-06-24 21:34:19 +02:00
|
|
|
TheISA::Kernel::Statistics *getKernelStats()
|
2009-09-15 07:44:48 +02:00
|
|
|
{ return thread->kernelStats; }
|
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
FunctionalPort *getPhysPort() { return thread->getPhysPort(); }
|
2009-09-15 07:44:48 +02:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
VirtualPort *getVirtPort();
|
2009-09-15 07:44:48 +02:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void connectMemPorts(ThreadContext *tc)
|
2010-06-24 21:34:12 +02:00
|
|
|
{ thread->connectMemPorts(tc); }
|
2009-09-15 07:44:48 +02:00
|
|
|
|
|
|
|
/** Dumps the function profiling information.
|
|
|
|
* @todo: Implement.
|
|
|
|
*/
|
2010-06-24 21:34:19 +02:00
|
|
|
void dumpFuncProfile();
|
2009-09-15 07:44:48 +02:00
|
|
|
|
|
|
|
/** Reads the last tick that this thread was activated on. */
|
2010-06-24 21:34:19 +02:00
|
|
|
Tick readLastActivate();
|
2009-09-15 07:44:48 +02:00
|
|
|
/** Reads the last tick that this thread was suspended on. */
|
2010-06-24 21:34:19 +02:00
|
|
|
Tick readLastSuspend();
|
2009-09-15 07:44:48 +02:00
|
|
|
|
|
|
|
/** Clears the function profiling information. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void profileClear();
|
2009-09-15 07:44:48 +02:00
|
|
|
|
|
|
|
/** Samples the function profiling information. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void profileSample();
|
2009-09-15 07:44:48 +02:00
|
|
|
|
|
|
|
/** Returns pointer to the quiesce event. */
|
2010-06-24 21:34:19 +02:00
|
|
|
EndQuiesceEvent *getQuiesceEvent()
|
2009-09-15 07:44:48 +02:00
|
|
|
{
|
|
|
|
return this->thread->quiesceEvent;
|
|
|
|
}
|
|
|
|
#else
|
2010-06-24 21:34:19 +02:00
|
|
|
TranslatingPort *getMemPort() { return thread->getMemPort(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Returns a pointer to this thread's process. */
|
2010-06-24 21:34:19 +02:00
|
|
|
Process *getProcessPtr() { return thread->getProcessPtr(); }
|
2009-09-15 07:44:48 +02:00
|
|
|
#endif
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Returns this thread's status. */
|
2010-06-24 21:34:19 +02:00
|
|
|
Status status() const { return thread->status(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Sets this thread's status. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void setStatus(Status new_status)
|
2009-02-11 00:49:29 +01:00
|
|
|
{ thread->setStatus(new_status); }
|
|
|
|
|
|
|
|
/** Set the status to Active. Optional delay indicates number of
|
|
|
|
* cycles to wait before beginning execution. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void activate(int delay = 1);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Set the status to Suspended. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void suspend(int delay = 0);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Set the status to Halted. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void halt(int delay = 0);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Takes over execution of a thread from another CPU. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void takeOverFrom(ThreadContext *old_context);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Registers statistics associated with this TC. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void regStats(const std::string &name);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Serializes state. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void serialize(std::ostream &os);
|
2009-03-05 04:37:45 +01:00
|
|
|
|
2009-02-11 00:49:29 +01:00
|
|
|
/** Unserializes state. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void unserialize(Checkpoint *cp, const std::string §ion);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Returns this thread's ID number. */
|
2010-06-24 21:34:19 +02:00
|
|
|
int getThreadNum() { return thread->readTid(); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Copies the architectural registers from another TC into this TC. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void copyArchRegs(ThreadContext *src_tc);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Resets all architectural registers to 0. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void clearArchRegs();
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Reads an integer register. */
|
2010-06-24 21:34:19 +02:00
|
|
|
uint64_t readIntReg(int reg_idx);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
FloatReg readFloatReg(int reg_idx);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
FloatRegBits readFloatRegBits(int reg_idx);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
uint64_t readRegOtherThread(int misc_reg, ThreadID tid);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Sets an integer register to a value. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void setIntReg(int reg_idx, uint64_t val);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void setFloatReg(int reg_idx, FloatReg val);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void setFloatRegBits(int reg_idx, FloatRegBits val);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void setRegOtherThread(int misc_reg,
|
2010-06-24 21:34:12 +02:00
|
|
|
const MiscReg &val,
|
2009-05-26 18:23:13 +02:00
|
|
|
ThreadID tid);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Reads this thread's PC. */
|
ISA,CPU,etc: Create an ISA defined PC type that abstracts out ISA behaviors.
This change is a low level and pervasive reorganization of how PCs are managed
in M5. Back when Alpha was the only ISA, there were only 2 PCs to worry about,
the PC and the NPC, and the lsb of the PC signaled whether or not you were in
PAL mode. As other ISAs were added, we had to add an NNPC, micro PC and next
micropc, x86 and ARM introduced variable length instruction sets, and ARM
started to keep track of mode bits in the PC. Each CPU model handled PCs in
its own custom way that needed to be updated individually to handle the new
dimensions of variability, or, in the case of ARMs mode-bit-in-the-pc hack,
the complexity could be hidden in the ISA at the ISA implementation's expense.
Areas like the branch predictor hadn't been updated to handle branch delay
slots or micropcs, and it turns out that had introduced a significant (10s of
percent) performance bug in SPARC and to a lesser extend MIPS. Rather than
perpetuate the problem by reworking O3 again to handle the PC features needed
by x86, this change was introduced to rework PC handling in a more modular,
transparent, and hopefully efficient way.
PC type:
Rather than having the superset of all possible elements of PC state declared
in each of the CPU models, each ISA defines its own PCState type which has
exactly the elements it needs. A cross product of canned PCState classes are
defined in the new "generic" ISA directory for ISAs with/without delay slots
and microcode. These are either typedef-ed or subclassed by each ISA. To read
or write this structure through a *Context, you use the new pcState() accessor
which reads or writes depending on whether it has an argument. If you just
want the address of the current or next instruction or the current micro PC,
you can get those through read-only accessors on either the PCState type or
the *Contexts. These are instAddr(), nextInstAddr(), and microPC(). Note the
move away from readPC. That name is ambiguous since it's not clear whether or
not it should be the actual address to fetch from, or if it should have extra
bits in it like the PAL mode bit. Each class is free to define its own
functions to get at whatever values it needs however it needs to to be used in
ISA specific code. Eventually Alpha's PAL mode bit could be moved out of the
PC and into a separate field like ARM.
These types can be reset to a particular pc (where npc = pc +
sizeof(MachInst), nnpc = npc + sizeof(MachInst), upc = 0, nupc = 1 as
appropriate), printed, serialized, and compared. There is a branching()
function which encapsulates code in the CPU models that checked if an
instruction branched or not. Exactly what that means in the context of branch
delay slots which can skip an instruction when not taken is ambiguous, and
ideally this function and its uses can be eliminated. PCStates also generally
know how to advance themselves in various ways depending on if they point at
an instruction, a microop, or the last microop of a macroop. More on that
later.
Ideally, accessing all the PCs at once when setting them will improve
performance of M5 even though more data needs to be moved around. This is
because often all the PCs need to be manipulated together, and by getting them
all at once you avoid multiple function calls. Also, the PCs of a particular
thread will have spatial locality in the cache. Previously they were grouped
by element in arrays which spread out accesses.
Advancing the PC:
The PCs were previously managed entirely by the CPU which had to know about PC
semantics, try to figure out which dimension to increment the PC in, what to
set NPC/NNPC, etc. These decisions are best left to the ISA in conjunction
with the PC type itself. Because most of the information about how to
increment the PC (mainly what type of instruction it refers to) is contained
in the instruction object, a new advancePC virtual function was added to the
StaticInst class. Subclasses provide an implementation that moves around the
right element of the PC with a minimal amount of decision making. In ISAs like
Alpha, the instructions always simply assign NPC to PC without having to worry
about micropcs, nnpcs, etc. The added cost of a virtual function call should
be outweighed by not having to figure out as much about what to do with the
PCs and mucking around with the extra elements.
One drawback of making the StaticInsts advance the PC is that you have to
actually have one to advance the PC. This would, superficially, seem to
require decoding an instruction before fetch could advance. This is, as far as
I can tell, realistic. fetch would advance through memory addresses, not PCs,
perhaps predicting new memory addresses using existing ones. More
sophisticated decisions about control flow would be made later on, after the
instruction was decoded, and handed back to fetch. If branching needs to
happen, some amount of decoding needs to happen to see that it's a branch,
what the target is, etc. This could get a little more complicated if that gets
done by the predecoder, but I'm choosing to ignore that for now.
Variable length instructions:
To handle variable length instructions in x86 and ARM, the predecoder now
takes in the current PC by reference to the getExtMachInst function. It can
modify the PC however it needs to (by setting NPC to be the PC + instruction
length, for instance). This could be improved since the CPU doesn't know if
the PC was modified and always has to write it back.
ISA parser:
To support the new API, all PC related operand types were removed from the
parser and replaced with a PCState type. There are two warts on this
implementation. First, as with all the other operand types, the PCState still
has to have a valid operand type even though it doesn't use it. Second, using
syntax like PCS.npc(target) doesn't work for two reasons, this looks like the
syntax for operand type overriding, and the parser can't figure out if you're
reading or writing. Instructions that use the PCS operand (which I've
consistently called it) need to first read it into a local variable,
manipulate it, and then write it back out.
Return address stack:
The return address stack needed a little extra help because, in the presence
of branch delay slots, it has to merge together elements of the return PC and
the call PC. To handle that, a buildRetPC utility function was added. There
are basically only two versions in all the ISAs, but it didn't seem short
enough to put into the generic ISA directory. Also, the branch predictor code
in O3 and InOrder were adjusted so that they always store the PC of the actual
call instruction in the RAS, not the next PC. If the call instruction is a
microop, the next PC refers to the next microop in the same macroop which is
probably not desirable. The buildRetPC function advances the PC intelligently
to the next macroop (in an ISA specific way) so that that case works.
Change in stats:
There were no change in stats except in MIPS and SPARC in the O3 model. MIPS
runs in about 9% fewer ticks. SPARC runs with 30%-50% fewer ticks, which could
likely be improved further by setting call/return instruction flags and taking
advantage of the RAS.
TODO:
Add != operators to the PCState classes, defined trivially to be !(a==b).
Smooth out places where PCs are split apart, passed around, and put back
together later. I think this might happen in SPARC's fault code. Add ISA
specific constructors that allow setting PC elements without calling a bunch
of accessors. Try to eliminate the need for the branching() function. Factor
out Alpha's PAL mode pc bit into a separate flag field, and eliminate places
where it's blindly masked out or tested in the PC.
2010-10-31 08:07:20 +01:00
|
|
|
TheISA::PCState pcState()
|
|
|
|
{ return cpu->pcState(thread->readTid()); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Sets this thread's PC. */
|
ISA,CPU,etc: Create an ISA defined PC type that abstracts out ISA behaviors.
This change is a low level and pervasive reorganization of how PCs are managed
in M5. Back when Alpha was the only ISA, there were only 2 PCs to worry about,
the PC and the NPC, and the lsb of the PC signaled whether or not you were in
PAL mode. As other ISAs were added, we had to add an NNPC, micro PC and next
micropc, x86 and ARM introduced variable length instruction sets, and ARM
started to keep track of mode bits in the PC. Each CPU model handled PCs in
its own custom way that needed to be updated individually to handle the new
dimensions of variability, or, in the case of ARMs mode-bit-in-the-pc hack,
the complexity could be hidden in the ISA at the ISA implementation's expense.
Areas like the branch predictor hadn't been updated to handle branch delay
slots or micropcs, and it turns out that had introduced a significant (10s of
percent) performance bug in SPARC and to a lesser extend MIPS. Rather than
perpetuate the problem by reworking O3 again to handle the PC features needed
by x86, this change was introduced to rework PC handling in a more modular,
transparent, and hopefully efficient way.
PC type:
Rather than having the superset of all possible elements of PC state declared
in each of the CPU models, each ISA defines its own PCState type which has
exactly the elements it needs. A cross product of canned PCState classes are
defined in the new "generic" ISA directory for ISAs with/without delay slots
and microcode. These are either typedef-ed or subclassed by each ISA. To read
or write this structure through a *Context, you use the new pcState() accessor
which reads or writes depending on whether it has an argument. If you just
want the address of the current or next instruction or the current micro PC,
you can get those through read-only accessors on either the PCState type or
the *Contexts. These are instAddr(), nextInstAddr(), and microPC(). Note the
move away from readPC. That name is ambiguous since it's not clear whether or
not it should be the actual address to fetch from, or if it should have extra
bits in it like the PAL mode bit. Each class is free to define its own
functions to get at whatever values it needs however it needs to to be used in
ISA specific code. Eventually Alpha's PAL mode bit could be moved out of the
PC and into a separate field like ARM.
These types can be reset to a particular pc (where npc = pc +
sizeof(MachInst), nnpc = npc + sizeof(MachInst), upc = 0, nupc = 1 as
appropriate), printed, serialized, and compared. There is a branching()
function which encapsulates code in the CPU models that checked if an
instruction branched or not. Exactly what that means in the context of branch
delay slots which can skip an instruction when not taken is ambiguous, and
ideally this function and its uses can be eliminated. PCStates also generally
know how to advance themselves in various ways depending on if they point at
an instruction, a microop, or the last microop of a macroop. More on that
later.
Ideally, accessing all the PCs at once when setting them will improve
performance of M5 even though more data needs to be moved around. This is
because often all the PCs need to be manipulated together, and by getting them
all at once you avoid multiple function calls. Also, the PCs of a particular
thread will have spatial locality in the cache. Previously they were grouped
by element in arrays which spread out accesses.
Advancing the PC:
The PCs were previously managed entirely by the CPU which had to know about PC
semantics, try to figure out which dimension to increment the PC in, what to
set NPC/NNPC, etc. These decisions are best left to the ISA in conjunction
with the PC type itself. Because most of the information about how to
increment the PC (mainly what type of instruction it refers to) is contained
in the instruction object, a new advancePC virtual function was added to the
StaticInst class. Subclasses provide an implementation that moves around the
right element of the PC with a minimal amount of decision making. In ISAs like
Alpha, the instructions always simply assign NPC to PC without having to worry
about micropcs, nnpcs, etc. The added cost of a virtual function call should
be outweighed by not having to figure out as much about what to do with the
PCs and mucking around with the extra elements.
One drawback of making the StaticInsts advance the PC is that you have to
actually have one to advance the PC. This would, superficially, seem to
require decoding an instruction before fetch could advance. This is, as far as
I can tell, realistic. fetch would advance through memory addresses, not PCs,
perhaps predicting new memory addresses using existing ones. More
sophisticated decisions about control flow would be made later on, after the
instruction was decoded, and handed back to fetch. If branching needs to
happen, some amount of decoding needs to happen to see that it's a branch,
what the target is, etc. This could get a little more complicated if that gets
done by the predecoder, but I'm choosing to ignore that for now.
Variable length instructions:
To handle variable length instructions in x86 and ARM, the predecoder now
takes in the current PC by reference to the getExtMachInst function. It can
modify the PC however it needs to (by setting NPC to be the PC + instruction
length, for instance). This could be improved since the CPU doesn't know if
the PC was modified and always has to write it back.
ISA parser:
To support the new API, all PC related operand types were removed from the
parser and replaced with a PCState type. There are two warts on this
implementation. First, as with all the other operand types, the PCState still
has to have a valid operand type even though it doesn't use it. Second, using
syntax like PCS.npc(target) doesn't work for two reasons, this looks like the
syntax for operand type overriding, and the parser can't figure out if you're
reading or writing. Instructions that use the PCS operand (which I've
consistently called it) need to first read it into a local variable,
manipulate it, and then write it back out.
Return address stack:
The return address stack needed a little extra help because, in the presence
of branch delay slots, it has to merge together elements of the return PC and
the call PC. To handle that, a buildRetPC utility function was added. There
are basically only two versions in all the ISAs, but it didn't seem short
enough to put into the generic ISA directory. Also, the branch predictor code
in O3 and InOrder were adjusted so that they always store the PC of the actual
call instruction in the RAS, not the next PC. If the call instruction is a
microop, the next PC refers to the next microop in the same macroop which is
probably not desirable. The buildRetPC function advances the PC intelligently
to the next macroop (in an ISA specific way) so that that case works.
Change in stats:
There were no change in stats except in MIPS and SPARC in the O3 model. MIPS
runs in about 9% fewer ticks. SPARC runs with 30%-50% fewer ticks, which could
likely be improved further by setting call/return instruction flags and taking
advantage of the RAS.
TODO:
Add != operators to the PCState classes, defined trivially to be !(a==b).
Smooth out places where PCs are split apart, passed around, and put back
together later. I think this might happen in SPARC's fault code. Add ISA
specific constructors that allow setting PC elements without calling a bunch
of accessors. Try to eliminate the need for the branching() function. Factor
out Alpha's PAL mode pc bit into a separate flag field, and eliminate places
where it's blindly masked out or tested in the PC.
2010-10-31 08:07:20 +01:00
|
|
|
void pcState(const TheISA::PCState &val)
|
|
|
|
{ cpu->pcState(val, thread->readTid()); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
ISA,CPU,etc: Create an ISA defined PC type that abstracts out ISA behaviors.
This change is a low level and pervasive reorganization of how PCs are managed
in M5. Back when Alpha was the only ISA, there were only 2 PCs to worry about,
the PC and the NPC, and the lsb of the PC signaled whether or not you were in
PAL mode. As other ISAs were added, we had to add an NNPC, micro PC and next
micropc, x86 and ARM introduced variable length instruction sets, and ARM
started to keep track of mode bits in the PC. Each CPU model handled PCs in
its own custom way that needed to be updated individually to handle the new
dimensions of variability, or, in the case of ARMs mode-bit-in-the-pc hack,
the complexity could be hidden in the ISA at the ISA implementation's expense.
Areas like the branch predictor hadn't been updated to handle branch delay
slots or micropcs, and it turns out that had introduced a significant (10s of
percent) performance bug in SPARC and to a lesser extend MIPS. Rather than
perpetuate the problem by reworking O3 again to handle the PC features needed
by x86, this change was introduced to rework PC handling in a more modular,
transparent, and hopefully efficient way.
PC type:
Rather than having the superset of all possible elements of PC state declared
in each of the CPU models, each ISA defines its own PCState type which has
exactly the elements it needs. A cross product of canned PCState classes are
defined in the new "generic" ISA directory for ISAs with/without delay slots
and microcode. These are either typedef-ed or subclassed by each ISA. To read
or write this structure through a *Context, you use the new pcState() accessor
which reads or writes depending on whether it has an argument. If you just
want the address of the current or next instruction or the current micro PC,
you can get those through read-only accessors on either the PCState type or
the *Contexts. These are instAddr(), nextInstAddr(), and microPC(). Note the
move away from readPC. That name is ambiguous since it's not clear whether or
not it should be the actual address to fetch from, or if it should have extra
bits in it like the PAL mode bit. Each class is free to define its own
functions to get at whatever values it needs however it needs to to be used in
ISA specific code. Eventually Alpha's PAL mode bit could be moved out of the
PC and into a separate field like ARM.
These types can be reset to a particular pc (where npc = pc +
sizeof(MachInst), nnpc = npc + sizeof(MachInst), upc = 0, nupc = 1 as
appropriate), printed, serialized, and compared. There is a branching()
function which encapsulates code in the CPU models that checked if an
instruction branched or not. Exactly what that means in the context of branch
delay slots which can skip an instruction when not taken is ambiguous, and
ideally this function and its uses can be eliminated. PCStates also generally
know how to advance themselves in various ways depending on if they point at
an instruction, a microop, or the last microop of a macroop. More on that
later.
Ideally, accessing all the PCs at once when setting them will improve
performance of M5 even though more data needs to be moved around. This is
because often all the PCs need to be manipulated together, and by getting them
all at once you avoid multiple function calls. Also, the PCs of a particular
thread will have spatial locality in the cache. Previously they were grouped
by element in arrays which spread out accesses.
Advancing the PC:
The PCs were previously managed entirely by the CPU which had to know about PC
semantics, try to figure out which dimension to increment the PC in, what to
set NPC/NNPC, etc. These decisions are best left to the ISA in conjunction
with the PC type itself. Because most of the information about how to
increment the PC (mainly what type of instruction it refers to) is contained
in the instruction object, a new advancePC virtual function was added to the
StaticInst class. Subclasses provide an implementation that moves around the
right element of the PC with a minimal amount of decision making. In ISAs like
Alpha, the instructions always simply assign NPC to PC without having to worry
about micropcs, nnpcs, etc. The added cost of a virtual function call should
be outweighed by not having to figure out as much about what to do with the
PCs and mucking around with the extra elements.
One drawback of making the StaticInsts advance the PC is that you have to
actually have one to advance the PC. This would, superficially, seem to
require decoding an instruction before fetch could advance. This is, as far as
I can tell, realistic. fetch would advance through memory addresses, not PCs,
perhaps predicting new memory addresses using existing ones. More
sophisticated decisions about control flow would be made later on, after the
instruction was decoded, and handed back to fetch. If branching needs to
happen, some amount of decoding needs to happen to see that it's a branch,
what the target is, etc. This could get a little more complicated if that gets
done by the predecoder, but I'm choosing to ignore that for now.
Variable length instructions:
To handle variable length instructions in x86 and ARM, the predecoder now
takes in the current PC by reference to the getExtMachInst function. It can
modify the PC however it needs to (by setting NPC to be the PC + instruction
length, for instance). This could be improved since the CPU doesn't know if
the PC was modified and always has to write it back.
ISA parser:
To support the new API, all PC related operand types were removed from the
parser and replaced with a PCState type. There are two warts on this
implementation. First, as with all the other operand types, the PCState still
has to have a valid operand type even though it doesn't use it. Second, using
syntax like PCS.npc(target) doesn't work for two reasons, this looks like the
syntax for operand type overriding, and the parser can't figure out if you're
reading or writing. Instructions that use the PCS operand (which I've
consistently called it) need to first read it into a local variable,
manipulate it, and then write it back out.
Return address stack:
The return address stack needed a little extra help because, in the presence
of branch delay slots, it has to merge together elements of the return PC and
the call PC. To handle that, a buildRetPC utility function was added. There
are basically only two versions in all the ISAs, but it didn't seem short
enough to put into the generic ISA directory. Also, the branch predictor code
in O3 and InOrder were adjusted so that they always store the PC of the actual
call instruction in the RAS, not the next PC. If the call instruction is a
microop, the next PC refers to the next microop in the same macroop which is
probably not desirable. The buildRetPC function advances the PC intelligently
to the next macroop (in an ISA specific way) so that that case works.
Change in stats:
There were no change in stats except in MIPS and SPARC in the O3 model. MIPS
runs in about 9% fewer ticks. SPARC runs with 30%-50% fewer ticks, which could
likely be improved further by setting call/return instruction flags and taking
advantage of the RAS.
TODO:
Add != operators to the PCState classes, defined trivially to be !(a==b).
Smooth out places where PCs are split apart, passed around, and put back
together later. I think this might happen in SPARC's fault code. Add ISA
specific constructors that allow setting PC elements without calling a bunch
of accessors. Try to eliminate the need for the branching() function. Factor
out Alpha's PAL mode pc bit into a separate flag field, and eliminate places
where it's blindly masked out or tested in the PC.
2010-10-31 08:07:20 +01:00
|
|
|
Addr instAddr()
|
|
|
|
{ return cpu->instAddr(thread->readTid()); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
ISA,CPU,etc: Create an ISA defined PC type that abstracts out ISA behaviors.
This change is a low level and pervasive reorganization of how PCs are managed
in M5. Back when Alpha was the only ISA, there were only 2 PCs to worry about,
the PC and the NPC, and the lsb of the PC signaled whether or not you were in
PAL mode. As other ISAs were added, we had to add an NNPC, micro PC and next
micropc, x86 and ARM introduced variable length instruction sets, and ARM
started to keep track of mode bits in the PC. Each CPU model handled PCs in
its own custom way that needed to be updated individually to handle the new
dimensions of variability, or, in the case of ARMs mode-bit-in-the-pc hack,
the complexity could be hidden in the ISA at the ISA implementation's expense.
Areas like the branch predictor hadn't been updated to handle branch delay
slots or micropcs, and it turns out that had introduced a significant (10s of
percent) performance bug in SPARC and to a lesser extend MIPS. Rather than
perpetuate the problem by reworking O3 again to handle the PC features needed
by x86, this change was introduced to rework PC handling in a more modular,
transparent, and hopefully efficient way.
PC type:
Rather than having the superset of all possible elements of PC state declared
in each of the CPU models, each ISA defines its own PCState type which has
exactly the elements it needs. A cross product of canned PCState classes are
defined in the new "generic" ISA directory for ISAs with/without delay slots
and microcode. These are either typedef-ed or subclassed by each ISA. To read
or write this structure through a *Context, you use the new pcState() accessor
which reads or writes depending on whether it has an argument. If you just
want the address of the current or next instruction or the current micro PC,
you can get those through read-only accessors on either the PCState type or
the *Contexts. These are instAddr(), nextInstAddr(), and microPC(). Note the
move away from readPC. That name is ambiguous since it's not clear whether or
not it should be the actual address to fetch from, or if it should have extra
bits in it like the PAL mode bit. Each class is free to define its own
functions to get at whatever values it needs however it needs to to be used in
ISA specific code. Eventually Alpha's PAL mode bit could be moved out of the
PC and into a separate field like ARM.
These types can be reset to a particular pc (where npc = pc +
sizeof(MachInst), nnpc = npc + sizeof(MachInst), upc = 0, nupc = 1 as
appropriate), printed, serialized, and compared. There is a branching()
function which encapsulates code in the CPU models that checked if an
instruction branched or not. Exactly what that means in the context of branch
delay slots which can skip an instruction when not taken is ambiguous, and
ideally this function and its uses can be eliminated. PCStates also generally
know how to advance themselves in various ways depending on if they point at
an instruction, a microop, or the last microop of a macroop. More on that
later.
Ideally, accessing all the PCs at once when setting them will improve
performance of M5 even though more data needs to be moved around. This is
because often all the PCs need to be manipulated together, and by getting them
all at once you avoid multiple function calls. Also, the PCs of a particular
thread will have spatial locality in the cache. Previously they were grouped
by element in arrays which spread out accesses.
Advancing the PC:
The PCs were previously managed entirely by the CPU which had to know about PC
semantics, try to figure out which dimension to increment the PC in, what to
set NPC/NNPC, etc. These decisions are best left to the ISA in conjunction
with the PC type itself. Because most of the information about how to
increment the PC (mainly what type of instruction it refers to) is contained
in the instruction object, a new advancePC virtual function was added to the
StaticInst class. Subclasses provide an implementation that moves around the
right element of the PC with a minimal amount of decision making. In ISAs like
Alpha, the instructions always simply assign NPC to PC without having to worry
about micropcs, nnpcs, etc. The added cost of a virtual function call should
be outweighed by not having to figure out as much about what to do with the
PCs and mucking around with the extra elements.
One drawback of making the StaticInsts advance the PC is that you have to
actually have one to advance the PC. This would, superficially, seem to
require decoding an instruction before fetch could advance. This is, as far as
I can tell, realistic. fetch would advance through memory addresses, not PCs,
perhaps predicting new memory addresses using existing ones. More
sophisticated decisions about control flow would be made later on, after the
instruction was decoded, and handed back to fetch. If branching needs to
happen, some amount of decoding needs to happen to see that it's a branch,
what the target is, etc. This could get a little more complicated if that gets
done by the predecoder, but I'm choosing to ignore that for now.
Variable length instructions:
To handle variable length instructions in x86 and ARM, the predecoder now
takes in the current PC by reference to the getExtMachInst function. It can
modify the PC however it needs to (by setting NPC to be the PC + instruction
length, for instance). This could be improved since the CPU doesn't know if
the PC was modified and always has to write it back.
ISA parser:
To support the new API, all PC related operand types were removed from the
parser and replaced with a PCState type. There are two warts on this
implementation. First, as with all the other operand types, the PCState still
has to have a valid operand type even though it doesn't use it. Second, using
syntax like PCS.npc(target) doesn't work for two reasons, this looks like the
syntax for operand type overriding, and the parser can't figure out if you're
reading or writing. Instructions that use the PCS operand (which I've
consistently called it) need to first read it into a local variable,
manipulate it, and then write it back out.
Return address stack:
The return address stack needed a little extra help because, in the presence
of branch delay slots, it has to merge together elements of the return PC and
the call PC. To handle that, a buildRetPC utility function was added. There
are basically only two versions in all the ISAs, but it didn't seem short
enough to put into the generic ISA directory. Also, the branch predictor code
in O3 and InOrder were adjusted so that they always store the PC of the actual
call instruction in the RAS, not the next PC. If the call instruction is a
microop, the next PC refers to the next microop in the same macroop which is
probably not desirable. The buildRetPC function advances the PC intelligently
to the next macroop (in an ISA specific way) so that that case works.
Change in stats:
There were no change in stats except in MIPS and SPARC in the O3 model. MIPS
runs in about 9% fewer ticks. SPARC runs with 30%-50% fewer ticks, which could
likely be improved further by setting call/return instruction flags and taking
advantage of the RAS.
TODO:
Add != operators to the PCState classes, defined trivially to be !(a==b).
Smooth out places where PCs are split apart, passed around, and put back
together later. I think this might happen in SPARC's fault code. Add ISA
specific constructors that allow setting PC elements without calling a bunch
of accessors. Try to eliminate the need for the branching() function. Factor
out Alpha's PAL mode pc bit into a separate flag field, and eliminate places
where it's blindly masked out or tested in the PC.
2010-10-31 08:07:20 +01:00
|
|
|
Addr nextInstAddr()
|
|
|
|
{ return cpu->nextInstAddr(thread->readTid()); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
ISA,CPU,etc: Create an ISA defined PC type that abstracts out ISA behaviors.
This change is a low level and pervasive reorganization of how PCs are managed
in M5. Back when Alpha was the only ISA, there were only 2 PCs to worry about,
the PC and the NPC, and the lsb of the PC signaled whether or not you were in
PAL mode. As other ISAs were added, we had to add an NNPC, micro PC and next
micropc, x86 and ARM introduced variable length instruction sets, and ARM
started to keep track of mode bits in the PC. Each CPU model handled PCs in
its own custom way that needed to be updated individually to handle the new
dimensions of variability, or, in the case of ARMs mode-bit-in-the-pc hack,
the complexity could be hidden in the ISA at the ISA implementation's expense.
Areas like the branch predictor hadn't been updated to handle branch delay
slots or micropcs, and it turns out that had introduced a significant (10s of
percent) performance bug in SPARC and to a lesser extend MIPS. Rather than
perpetuate the problem by reworking O3 again to handle the PC features needed
by x86, this change was introduced to rework PC handling in a more modular,
transparent, and hopefully efficient way.
PC type:
Rather than having the superset of all possible elements of PC state declared
in each of the CPU models, each ISA defines its own PCState type which has
exactly the elements it needs. A cross product of canned PCState classes are
defined in the new "generic" ISA directory for ISAs with/without delay slots
and microcode. These are either typedef-ed or subclassed by each ISA. To read
or write this structure through a *Context, you use the new pcState() accessor
which reads or writes depending on whether it has an argument. If you just
want the address of the current or next instruction or the current micro PC,
you can get those through read-only accessors on either the PCState type or
the *Contexts. These are instAddr(), nextInstAddr(), and microPC(). Note the
move away from readPC. That name is ambiguous since it's not clear whether or
not it should be the actual address to fetch from, or if it should have extra
bits in it like the PAL mode bit. Each class is free to define its own
functions to get at whatever values it needs however it needs to to be used in
ISA specific code. Eventually Alpha's PAL mode bit could be moved out of the
PC and into a separate field like ARM.
These types can be reset to a particular pc (where npc = pc +
sizeof(MachInst), nnpc = npc + sizeof(MachInst), upc = 0, nupc = 1 as
appropriate), printed, serialized, and compared. There is a branching()
function which encapsulates code in the CPU models that checked if an
instruction branched or not. Exactly what that means in the context of branch
delay slots which can skip an instruction when not taken is ambiguous, and
ideally this function and its uses can be eliminated. PCStates also generally
know how to advance themselves in various ways depending on if they point at
an instruction, a microop, or the last microop of a macroop. More on that
later.
Ideally, accessing all the PCs at once when setting them will improve
performance of M5 even though more data needs to be moved around. This is
because often all the PCs need to be manipulated together, and by getting them
all at once you avoid multiple function calls. Also, the PCs of a particular
thread will have spatial locality in the cache. Previously they were grouped
by element in arrays which spread out accesses.
Advancing the PC:
The PCs were previously managed entirely by the CPU which had to know about PC
semantics, try to figure out which dimension to increment the PC in, what to
set NPC/NNPC, etc. These decisions are best left to the ISA in conjunction
with the PC type itself. Because most of the information about how to
increment the PC (mainly what type of instruction it refers to) is contained
in the instruction object, a new advancePC virtual function was added to the
StaticInst class. Subclasses provide an implementation that moves around the
right element of the PC with a minimal amount of decision making. In ISAs like
Alpha, the instructions always simply assign NPC to PC without having to worry
about micropcs, nnpcs, etc. The added cost of a virtual function call should
be outweighed by not having to figure out as much about what to do with the
PCs and mucking around with the extra elements.
One drawback of making the StaticInsts advance the PC is that you have to
actually have one to advance the PC. This would, superficially, seem to
require decoding an instruction before fetch could advance. This is, as far as
I can tell, realistic. fetch would advance through memory addresses, not PCs,
perhaps predicting new memory addresses using existing ones. More
sophisticated decisions about control flow would be made later on, after the
instruction was decoded, and handed back to fetch. If branching needs to
happen, some amount of decoding needs to happen to see that it's a branch,
what the target is, etc. This could get a little more complicated if that gets
done by the predecoder, but I'm choosing to ignore that for now.
Variable length instructions:
To handle variable length instructions in x86 and ARM, the predecoder now
takes in the current PC by reference to the getExtMachInst function. It can
modify the PC however it needs to (by setting NPC to be the PC + instruction
length, for instance). This could be improved since the CPU doesn't know if
the PC was modified and always has to write it back.
ISA parser:
To support the new API, all PC related operand types were removed from the
parser and replaced with a PCState type. There are two warts on this
implementation. First, as with all the other operand types, the PCState still
has to have a valid operand type even though it doesn't use it. Second, using
syntax like PCS.npc(target) doesn't work for two reasons, this looks like the
syntax for operand type overriding, and the parser can't figure out if you're
reading or writing. Instructions that use the PCS operand (which I've
consistently called it) need to first read it into a local variable,
manipulate it, and then write it back out.
Return address stack:
The return address stack needed a little extra help because, in the presence
of branch delay slots, it has to merge together elements of the return PC and
the call PC. To handle that, a buildRetPC utility function was added. There
are basically only two versions in all the ISAs, but it didn't seem short
enough to put into the generic ISA directory. Also, the branch predictor code
in O3 and InOrder were adjusted so that they always store the PC of the actual
call instruction in the RAS, not the next PC. If the call instruction is a
microop, the next PC refers to the next microop in the same macroop which is
probably not desirable. The buildRetPC function advances the PC intelligently
to the next macroop (in an ISA specific way) so that that case works.
Change in stats:
There were no change in stats except in MIPS and SPARC in the O3 model. MIPS
runs in about 9% fewer ticks. SPARC runs with 30%-50% fewer ticks, which could
likely be improved further by setting call/return instruction flags and taking
advantage of the RAS.
TODO:
Add != operators to the PCState classes, defined trivially to be !(a==b).
Smooth out places where PCs are split apart, passed around, and put back
together later. I think this might happen in SPARC's fault code. Add ISA
specific constructors that allow setting PC elements without calling a bunch
of accessors. Try to eliminate the need for the branching() function. Factor
out Alpha's PAL mode pc bit into a separate flag field, and eliminate places
where it's blindly masked out or tested in the PC.
2010-10-31 08:07:20 +01:00
|
|
|
MicroPC microPC()
|
|
|
|
{ return cpu->microPC(thread->readTid()); }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Reads a miscellaneous register. */
|
2010-06-24 21:34:19 +02:00
|
|
|
MiscReg readMiscRegNoEffect(int misc_reg)
|
2009-02-11 00:49:29 +01:00
|
|
|
{ return cpu->readMiscRegNoEffect(misc_reg, thread->readTid()); }
|
|
|
|
|
|
|
|
/** Reads a misc. register, including any side-effects the
|
|
|
|
* read might have as defined by the architecture. */
|
2010-06-24 21:34:19 +02:00
|
|
|
MiscReg readMiscReg(int misc_reg)
|
2009-02-11 00:49:29 +01:00
|
|
|
{ return cpu->readMiscReg(misc_reg, thread->readTid()); }
|
|
|
|
|
|
|
|
/** Sets a misc. register. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void setMiscRegNoEffect(int misc_reg, const MiscReg &val);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Sets a misc. register, including any side-effects the
|
|
|
|
* write might have as defined by the architecture. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void setMiscReg(int misc_reg, const MiscReg &val);
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
int flattenIntIndex(int reg)
|
2009-07-09 08:02:20 +02:00
|
|
|
{ return cpu->isa[thread->readTid()].flattenIntIndex(reg); }
|
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
int flattenFloatIndex(int reg)
|
2009-07-09 08:02:20 +02:00
|
|
|
{ return cpu->isa[thread->readTid()].flattenFloatIndex(reg); }
|
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void activateContext(int delay)
|
2009-02-11 00:49:29 +01:00
|
|
|
{ cpu->activateContext(thread->readTid(), delay); }
|
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void deallocateContext()
|
2009-02-11 00:49:29 +01:00
|
|
|
{ cpu->deallocateContext(thread->readTid()); }
|
|
|
|
|
|
|
|
/** Returns the number of consecutive store conditional failures. */
|
|
|
|
// @todo: Figure out where these store cond failures should go.
|
2010-06-24 21:34:19 +02:00
|
|
|
unsigned readStCondFailures()
|
2009-02-11 00:49:29 +01:00
|
|
|
{ return thread->storeCondFailures; }
|
|
|
|
|
|
|
|
/** Sets the number of consecutive store conditional failures. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void setStCondFailures(unsigned sc_failures)
|
2009-02-11 00:49:29 +01:00
|
|
|
{ thread->storeCondFailures = sc_failures; }
|
|
|
|
|
|
|
|
// Only really makes sense for old CPU model. Lots of code
|
|
|
|
// outside the CPU still checks this function, so it will
|
|
|
|
// always return false to keep everything working.
|
|
|
|
/** Checks if the thread is misspeculating. Because it is
|
|
|
|
* very difficult to determine if the thread is
|
|
|
|
* misspeculating, this is set as false. */
|
2010-06-24 21:34:19 +02:00
|
|
|
bool misspeculating() { return false; }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2009-09-15 07:44:48 +02:00
|
|
|
#if !FULL_SYSTEM
|
2009-02-11 00:49:29 +01:00
|
|
|
/** Executes a syscall in SE mode. */
|
2010-06-24 21:34:19 +02:00
|
|
|
void syscall(int64_t callnum)
|
2009-02-11 00:49:29 +01:00
|
|
|
{ return cpu->syscall(callnum, thread->readTid()); }
|
2009-09-15 07:44:48 +02:00
|
|
|
#endif
|
2009-02-11 00:49:29 +01:00
|
|
|
|
|
|
|
/** Reads the funcExeInst counter. */
|
2010-06-24 21:34:19 +02:00
|
|
|
Counter readFuncExeInst() { return thread->funcExeInst; }
|
2009-02-11 00:49:29 +01:00
|
|
|
|
2010-06-24 21:34:19 +02:00
|
|
|
void changeRegFileContext(unsigned param,
|
2009-02-11 00:49:29 +01:00
|
|
|
unsigned val)
|
|
|
|
{ panic("Not supported!"); }
|
|
|
|
};
|
|
|
|
|
|
|
|
#endif
|