In gems1.4, the version management logs are stored in the simulator data
structures. see $GEMS/ruby/log_tm/TransactionLog.C
Gems2.0, the VM logs are stored in software data structures of the
simulated program. GEMS accesses the logs using SIMICS API
calls to read and write physical memory. see
$GEMS/ruby/log_tm/TransactionVersionManager.C. There is no function
currently
to print out the log of a transactional thread. However, with a little
tweaking you can modify hardwareRollback() method
to 'only' print out the log instead of rolling back.
Jayaram
Irene-Aggeliki Chounta wrote:
hello all.
I'm working on LogTM both on gems1.4 and gems2.0.
I would like to view the log files that are kept by gems during
hardware transactions and track them down.
Is anyone aware how can I do that?
thank you.
-------------------------------------------------------------------
irene.
......in accordance with the prophecy.
------------------------------------------------------------------------
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
|