> On 2011-03-31 12:27:47, Nilay Vaish wrote: > > Is context Id being used any where?
Not in any of the stock-provided protocols, but in some of our internal protocols, yes. This would also enable anyone to do context-based cache management, if they so desired, though it's not in the tree at all. This is just to provide the functionality, now people can use it however they want! - Lisa ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/623/#review1060 ----------------------------------------------------------- On 2011-03-31 12:16:27, Lisa Hsu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.m5sim.org/r/623/ > ----------------------------------------------------------- > > (Updated 2011-03-31 12:16:27) > > > Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and > Nathan Binkert. > > > Summary > ------- > > Ruby: pass Packet->Req->contextId() to Ruby. > It is useful for Ruby to understand from whence request packets came. > This has all request packets going into Ruby pass the contextId value, if > it exists. This supplants the old libruby proc_id value passed around in > all the Messages, so I've also removed the unused unsigned proc_id; member > generated by SLICC for all Message types. > > > Diffs > ----- > > src/mem/protocol/RubySlicc_Types.sm d8587c913ccf > src/mem/ruby/slicc_interface/RubyRequest.hh d8587c913ccf > src/mem/ruby/system/Sequencer.cc d8587c913ccf > src/mem/slicc/symbols/Type.py d8587c913ccf > > Diff: http://reviews.m5sim.org/r/623/diff > > > Testing > ------- > > > Thanks, > > Lisa > > _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
