It should definitely be do-able with a modest amount of effort.
We already use Ruby as a standalone memory hierarchy when using the Tester
driver. The main entry point is the Ruby sequencer
($GEMS/ruby/system/Sequencer.C) which acts as the processor interface.
Drivers issue requests to Ruby via Sequencer::makeRequest. The Sequencer
calls hitCallback() on the drivers when the request has finished.
All the Simics/Ruby interface is in $GEMS/ruby/simics. You can see where
the Sequencer::makeRequest() call is made in the SimicsProcessor.C
This is a quick response. If you have more specific questions, do ask
them.
--Mike
> Hi,
>
> I would like to use Ruby as a standalone memory hierarchy simulator API.
> I'd like to use this API with PIN. Can you give me a sense of how much
> work is involved and where to start? Thanks,
>
> Osvaldo
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>
|