Re: [Gems-users] error with setting g_NUM_SMT_THREADS

[Muhammad abid Mughal <mabidm_pieas@xxxxxxxxx>]

To the best of knowledge, g_NUM_SMT_THREADS parameter  only valid for Opal processor.

There may be some other reason of this error "Segmentation fault (SIGSEGV) int main thread"".

Best ,

Muhamma abid

---

From: lenglihello <lenglihello@xxxxxxx>
To: GEMS_USERS <gems-users@xxxxxxxxxxx>
Sent: Friday, July 24, 2009 17:17:06
Subject: [Gems-users] error with setting g_NUM_SMT_THREADS

hi, every one

 

I encounter a problem with "g_NUM_SMT_THREADS ". To test with multi-threads, I set "g_NUM_SMT_THREADS=2", and simics failed with "Segmentation fault (SIGSEGV) int main thread". But it works well with "g_NUM_SMT_THREADS=1". I worked with simics-3.0.1 and gems 2.1, gcc-4.1.2, target machine is solaris10, sparc.  I want to know if there is something error in my ruby initiate? any help will be apreciated!
***************************************

istc-disable

dstc-disable

magic-break-disable

cpu-switch-time 1

magic-break-enable

read-configuration solaris_checkpoint_zc/solaris10_2p_gcc1.conf 

 

load-module ruby

ruby0.setparam g_NUM_PROCESSORS 2

ruby0.setparam g_MEMORY_SIZE_BYTES 2147483648

ruby0.setparam g_PROCS_PER_CHIP 2

ruby0.setparam g_NUM_SMT_THREADS 2

ruby0.setparam NUMBER_OF_VIRTUAL_NETWORKS 5

ruby0.setparam XACT_DEBUG_LEVEL 0

ruby0.setparam_str PROFILE_XACT true

ruby0.setparam_str XACT_MEMORY true

ruby0.setparam_str XACT_LAZY_VM true

ruby0.setparam_str XACT_EAGER_CD true

ruby0.setparam_str REMOVE_SINGLE_CYCLE_DCACHE_FAST_PATH true

ruby0.setparam_str XACT_CONFLICT_RES BASE

ruby0.setparam_str USER_MODE_DATA_ONLY true

#ruby0.setparam_str XACT_ISOLATION_CHECK true

ruby0.init

ruby0.debug-output-file /root/gems/simics_3_workspace/output_file/2p_output

c

*************************************

 

2009-07-24

---

lenglihello

---

  Get your new Email address!  
Grab the Email name you've always wanted before someone else does!