Re: [Gems-users] ATMTP: Problem with strange Transaction-Aborts

[Philipp Tölke <toelke+gems@xxxxxxxxx>]

> I think it would be useful to get more debugging output from the simulator.
> Please turn on XACT_DEBUG and set XACT_DEBUG_LEVEL to 2 or 3.
> PROFILE_EXCEPTIONS should let you know if a TLB-miss is happening in your
> simulation.
> http://www.cs.wisc.edu/gems/doc/gems-wiki/moin.cgi/Transactional_Memory

This is the complete output with 

XACT_DEBUG=true
XACT_DEBUG_LEVEL=2
PROFILE_EXCEPTIONS=true

:

simics> step-instruction
6826445428   0 [0,0] TID -1 XACT ABORT 0 caused by 0 [ 0, 0 ] xid: 0
address: [0x0, line 0x0] delay: 6826445428  PC [0x0, line 0x0]  *PC 0x0
'illtrap 0'

I will try with XACT_DEBUG_LEVEL=3.

> I wouldn't worry too much about the zeros, since with ATMTP, the appropriate
> values are not send to the profiler method (profileAbortTransaction() at
> TransactionInterfaceManager.C). Having said that, it would be good to modify
> the code to fix this issue and get more information about the exact PC where
> your abort is happening.

Then why does the simulation hang, instead of just aborting the
transaction?

Thank you for your help so far!

Regards,
-- 
Philipp Tölke

Attachment: signature.asc
Description: Digital signature