Re: [Gems-users] results of microbenchmarks deque-tm

[Jayaram Bobba <bobba@xxxxxxxxxxx>]

Yes. The binary is executing a magic instruction that causes SIMICS to 
break the execution.
Can you disassemble the PC address 0x10f58 and see which portion of the 
code it belongs to?
That should give you an idea of why the simulation was stopped.

Note that the 'transaction' you see on the screen output refers to a 
workload transaction which is
different from LogTM transactions.

Jayaram

Irene-Aggeliki Chounta wrote:
> hi everyone,
>  
> I'm experimenting with protocol MESI_SMP_LogTM and currently running 
> deque-tm to check out how it works.
>  
> I make the needed changes to simics script, copy the binary to 
> simulated machine and execute and then I get in simics host the following:
>  
> end_transaction_magic_call: Unexpected magic call number 4
> end_transaction_magic_call: transaction started: 0, transaction 
> completed: 0, transaction_limit: 4, None
> [cpu2] v:0x0000000000010f58 p:0x00000003f95b4f58  magic (sethi 
> 0x40000, %g0)
> simics>
>  
> so from what i can understand there's no transaction started due to 
> this unexpected magic call number 4, is that correct????
>  
> why is this happening anyway????
>  
> thanks in advance.
>  
> ps. happy new year all ;)
>  
>  
> -------------------------------------------------------------------
> 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.
>
>