Date: | Thu, 23 Oct 2008 16:46:39 -0500 |
---|---|
From: | "Mike Marty" <mike.marty@xxxxxxxxx> |
Subject: | Re: [Gems-users] SLICC question |
Yes, but doing so is playing with fire. The state is queried by getState(). If a TBE is allocated, the state is pulled from the TBE entry. Otherwise if a cache block is allocate, the state is pulled from the State field in the CacheEntry. Otherwise State:NP is typically returned.
You could directly manipulate the cache block's state by accessing the TBEEntry or CacheEntry directly. I.e. L2cacheMemory[different_address].State := State:MY_MESSED_UP_STATE; --Mike On Thu, Oct 23, 2008 at 12:03 PM, Lois Orosa Nogueira <lois.orosa@xxxxxx> wrote: Hi list, |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] Having more than one cache request go out simultaniously per processor, Fuad Tabba |
---|---|
Next by Date: | Re: [Gems-users] Having more than one cache request go out simultaniously per processor, Dan Gibson |
Previous by Thread: | [Gems-users] SLICC question, Lois Orosa Nogueira |
Next by Thread: | [Gems-users] SLICC: explanation for deallocating certain blocks, Fuad Tabba |
Indexes: | [Date] [Thread] |