Re: [Gems-users] Processor number in Opal

[Muhammad abid Mughal <mabidm_pieas@xxxxxxxxx>]

use the same ruby parameters  (g_PROCS_PER_CHIP, g_NUM_PROCESSORS)  to specify number of Opal processor

Use same value for g_NUM_SMT_THREADS and CONFIG_LOGICAL_PER_PHY_PROC

 SIM_number_processor() always returns 1 because you are using single processor checkpoint

if you are using 4 Opal processors (and each processor has 4 threads) then simics checkpoint must have 16 processors.

Regards

Muhammad abid

---

From: Amy Pang <pangjiufeng@xxxxxxxxxxxxxxx>
To: gems-users@xxxxxxxxxxx
Sent: Thursday, May 27, 2010 16:22:04
Subject: [Gems-users] Processor number in Opal

Hi list,

I find that the simulated processor number in Ruby could be set in $GEMS/ruby/config/rubyconfig.

default through two parameters (g_PROCS_PER_CHIP, g_NUM_PROCESSORS) and could be changed after booting up Simics. And the simulated processor number in Ruby should be same as that of Simics.

But how could you set simulated processor number in Opal? In $GEMS/opal/config/config.default, there is only CONFIG_LOGICAL_PER_PHY_PROC which is defined for SMT.  In $GEMS/opal/system/system.C line 207 SIM_number_processor() always returns 1, which is used as Opal as the processor number in the system.  That might dismatch with Ruby and Simics.

I am  new to GEMS and appreciate your help.

--
-Amy Pang