| | | Ruby: Correctly set access permissions for directory entries
|
| | | The access permissions for the directory entries are not being set correctly.
|
| | | This is because pointers are not used for handling directory entries.
|
| | | function. The setState() function will once again set the permissions as well.
|
| | | But it would make use of the State_to_permission() function, instead of doing
|
| | | the analysis it used to do earlier. The changePermission() function provided
|
| | | by the AbstractEntry and AbstractCacheEntry classes has been exposed to SLICC
|
| | | code once again. The set_permission() functionality has been removed. |
| | |
|
| ~ | | I have done this only for the MESI protocol so far. Once we build a consensus
|
| ~ | | one the changes, I will make changes to other protocols as well. |
| | ~ | The patch has been updated to set permissions for all the five protocols.
|
| | ~ | All the protocols compile and clears 10000 loads. |
| - | |
|
| - | | As far as testing is concerned, the protocol compiles and clears 10000 loads.
|
| - | | I did not test any more than that. |
| - | |
|
| - | | A point that I wanted to raise for discussion: I think we should pull State
|
| - | | enum and the accompanying functions into the Machine it self. Brad, what do
|
| - | | you think? |
