cache: don't allow dirty data in the i-cache
Review Request #1284 - Created July 2, 2012 and submitted - Latest diff uploaded
| Information | |
|---|---|
| Tony Gutierrez | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9086:8a09d8787f5a --------------------------- cache: don't allow dirty data in the i-cache removes the optimization that forwards an exclusive copy to a requester on a read, only for the i-cache. this optimization isn't necessary because we typically won't be writing to the i-cache.
Added i-cache invalidation instruction for ARM. These instructions invalidate i-cache entries without writing them back, because it is not expected for there to be dirty data in the caches. While invalidating I would get assert failures and/or the program would hang due to dirty data in the i-cache being invalidated. Doing this fixed those problems. Ran BBench to completion with this fix and inv instructions in place. This is a necessary step towards adding the inv instructions for ARM.