diff options
| author | Lisa Hsu <hsul@eecs.umich.edu> | 2008-11-02 21:57:07 -0500 |
|---|---|---|
| committer | Lisa Hsu <hsul@eecs.umich.edu> | 2008-11-02 21:57:07 -0500 |
| commit | d857faf073895dcfde97141bd6346fe5d4317f8e (patch) | |
| tree | bfcd9fadba95b409721597948dd46cfda3744ee0 /src/arch/alpha/locked_mem.hh | |
| parent | 67fda02dda290d614de233846fee434b3713b1dc (diff) | |
| download | gem5-d857faf073895dcfde97141bd6346fe5d4317f8e.tar.xz | |
Add in Context IDs to the simulator. From now on, cpuId is almost never used,
the primary identifier for a hardware context should be contextId(). The
concept of threads within a CPU remains, in the form of threadId() because
sometimes you need to know which context within a cpu to manipulate.
Diffstat (limited to 'src/arch/alpha/locked_mem.hh')
| -rw-r--r-- | src/arch/alpha/locked_mem.hh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/arch/alpha/locked_mem.hh b/src/arch/alpha/locked_mem.hh index 6f4f5a748..e8928ba08 100644 --- a/src/arch/alpha/locked_mem.hh +++ b/src/arch/alpha/locked_mem.hh @@ -85,9 +85,9 @@ handleLockedWrite(XC *xc, Request *req) stCondFailures++; xc->setStCondFailures(stCondFailures); if (stCondFailures % 100000 == 0) { - warn("cpu %d: %d consecutive " + warn("context %d: %d consecutive " "store conditional failures\n", - xc->cpuId(), stCondFailures); + xc->contextId(), stCondFailures); } // store conditional failed already, so don't issue it to mem |