> On May 12, 2015, 2:59 p.m., Jason Power wrote: > > I think this seems reasonable. For instance, if you want to create a single > > state machine with both an L3 and a directory (e.g., the directory is the > > L3 cache tags), this would be useful. I could see many other use cases as > > well. > > > > Assuming this gets through the review process, it would be good to add a > > note to the wiki about the changes in the SLICC syntax. > > Joel Hestness wrote: > I don't understand your example. If the directory is the L3 cache tags, > then you should only need 1 entry type with a variable indicating presence in > the L3.
I'm happy to add this description to the wiki if it helps. - Brad ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2794/#review6169 ----------------------------------------------------------- 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
