Re: [Gems-users] Transactional Memory

[Jayaram Bobba <bobba@xxxxxxxxxxx>]

Have you followed the steps indicated here...
http://www.cs.wisc.edu/gems/doc/gems-wiki/moin.cgi/TM_Workload_Setup

Specifically, are you calling set_transaction_registers()?

This should pass the max log size information to the simulator. Check
setLogBase in ruby/log_tm/TransactionVersionManager.C

Jayaram

Mishali Naik wrote:
> Hi all,
>            I would like to run an experiment with Eager Version 
> Management and Eager Conflict Detection. I have been getting this 
> assertion failure:
> "simics-common: log_tm/TransactionVersionManager.C:209: bool 
> TransactionVersionManager::addLogEntry(int, int, Vector<uint32>&):
> Assertion `m_logSize[thread] < (m_maxLogSize[thread] * 1024)' failed."
>
> I traced through the code and I see that m_maxLogSize variable should 
> get initialized here "  m_maxLogSize[thread] = (int) 
> SIMICS_read_register(proc_no, rn_g5); "
> But the value for m_maxLogSize is 0 when the assertion fails.
>
>
> It would be great if someone could point out what am I missing in 
> configuring the experiment? Thanks in advance for your help.
> - Mishali
> _______________________________________________
> 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.
>