The L2 cache size is set in the L2 controller specification:
CacheMemory L2cacheMemory, template_hack="<L2Cache_Entry>",
constructor_hack='L2_CACHE_NUM_SETS_BITS,L2_CACHE_ASSOC,MachineType_L2Cache,int_to_string(i)';
This is instantiated for each controller. To do what you want, perhaps
you should set the size in CacheMemory.h based on the passed parameter.
For example, do this (using the hidden "i" parameter that is used for
the name of the cache object):
CacheMemory L2cacheMemory, template_hack="<L2Cache_Entry>",
constructor_hack='i, MachineType_L2Cache,int_to_string(i)';
Hi!
Suppose we have several L2s, I would like to modify just 1 of the
L2 cache sizes in MSI_MOSI_CMP_directory. ( I could also say I would
like to modify block size, associativity or other parameters). Should I
modify the protocol specification (via the SLICC utility) or should I
modify the generated codes? What is the most appropriated?
Your help will be greatly appreciated!
Thanks,
Mario
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.