> 2007/4/12, Dave Z. <zhu_dave@xxxxxxxxx>:
> Hello All,
> As I understand Simics delivers data/instruction
> fetches to Ruby and these data/instruction fetches are
> recorded by SimicsDriver, right? Could you please
> clarify the following?
SimicsDriver is the interface between Simics and Ruby, that means it is the interface between processor and memory.
> - Do these requests recorded by SimicsDriver only come
> from Simics? Or are there some Ruby requests which
> might get recorded by SimicsDriver as well?
> - When sending data from one processor to another
> (e_sendData), does it involve SimicsDriver?
> - When Ruby models the data allocation and data
> movement behaviors such as cache line allocation,
> L1_to_L2, L2_replacement, etc., are these requests
> sent back to Simics? Or recorded by SimicsDriver?
SimicsDriver only record memory transition request from Simics and send it to Ruby. And when Ruby finishes a memory transition, it will call SimicsDriver and wakeup Simics. Those internal operations caused by the memory transition in ruby will not call SimicsDriver.
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}