> On May 12, 2015, 2:13 p.m., Joel Hestness wrote: > > Can you give a more detailed description of the use case? In what scenario > > do you want separate entry types?
As Jason points out below, this type of situation can happen in many scenarios. Joel your idea would require that the directory and cache tags be manged by a single structure. That may not be what one always wants to do. - Brad ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2794/#review6150 ----------------------------------------------------------- On May 11, 2015, 10:21 p.m., Tony Gutierrez wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/2794/ > ----------------------------------------------------------- > > (Updated May 11, 2015, 10:21 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 10851:88582222762b > --------------------------- > slicc: support for multiple cache entry types in the same state machine > > To have multiple Entry types (e.g., a cache Entry type and > a directory Entry type), just declare one of them as a secondary > type by using the pair 'main="false"', e.g.: > > structure(DirEntry, desc="...", interface="AbstractCacheEntry", > main="false") { > > ...and the primary type would be declared: > > structure(Entry, desc="...", interface="AbstractCacheEntry") { > > > Diffs > ----- > > src/mem/slicc/symbols/StateMachine.py > fbdaa08aaa426b9f4660c366f934ccb670d954ec > > Diff: http://reviews.gem5.org/r/2794/diff/ > > > Testing > ------- > > > Thanks, > > Tony Gutierrez > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
