Ricardo,
    This parameter refers to workload transactions, and is not TM-specific. 
It is used to stop simulation after a certain number of workload 
transactions (e.g. units of work) have been reached.
    Placing a special Simics magic instruction (with magic number 0x5 or 
0x5000, I don't remember) in your program's source code will increment a 
counter in mfacet.py, which denotes the end of a workload transaction.
    When used in conjuction with setup_run_for_n_transactions() on the 
Simics command line, simulation will halt after your predefined number of workload 
transactions.
   Luke
On Thu, 29 Nov 2007, Ricardo Quislant del Barrio wrote:
 
Hello, my question is the next:
what does "num_xact" refer to?
In "config.py" file, when you are filling the "microbenchmark_list" with
your microbenchmarks, you are required to set the name of the benchmark,
its command line parameters and so on. Among these parameters you can
find the "num_xact" parameter.
I would like to know if this parameter refers to the number of
BEGIN_WORKLOAD_TRANSACTION/END_WORKLOAD_TRANSACTION pairs the
microbenchmark will rise or, otherwise, to the number of
BEGIN_TRANSACTION(id)/COMMIT_TRANSACTION(id) pairs.
Thanks, Ricardo Quislant.
_______________________________________________
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.
  
 |