diff options
author | Lisa Hsu <Lisa.Hsu@amd.com> | 2011-09-02 17:04:00 -0700 |
---|---|---|
committer | Lisa Hsu <Lisa.Hsu@amd.com> | 2011-09-02 17:04:00 -0700 |
commit | 365966304e37d05f5e9e1f987a5956d55ea5f2c7 (patch) | |
tree | 92666f0d610ba1b1e4987750bc6a312a3971e977 /src/sim/process.cc | |
parent | f6a2ef22ffc70d2467a2b9c0bc1532f73be067b5 (diff) | |
download | gem5-365966304e37d05f5e9e1f987a5956d55ea5f2c7.tar.xz |
TLB: comments and a helpful warning.
Nothing big here, but when you have an address that is not in the page table request to be allocated, if it falls outside of the maximum stack range all you get is a page fault and you don't know why. Add a little warn() to explain it a bit. Also add some comments and alter logic a little so that you don't totally ignore the return value of checkAndAllocNextPage().
Diffstat (limited to 'src/sim/process.cc')
-rw-r--r-- | src/sim/process.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/sim/process.cc b/src/sim/process.cc index 28142d731..bec33c70b 100644 --- a/src/sim/process.cc +++ b/src/sim/process.cc @@ -351,6 +351,7 @@ Process::checkAndAllocNextPage(Addr vaddr) }; return true; } + warn("Not increasing stack: requested vaddr is outside of stack range."); return false; } |