Re: [Gems-users] 64 cores on gems 2.1.1 with simics 3.0


Date: Fri, 5 Nov 2010 20:45:44 -0500
From: Rakesh Komuravelli <komurav1@xxxxxxxxxxxx>
Subject: Re: [Gems-users] 64 cores on gems 2.1.1 with simics 3.0
I don't think it has to do with running on 64 cores. It looks more like a bug in the protocol. Its just that running on 64 cores hit a case which uncovered the bug.

Thanks,
Rakesh

On Fri, Nov 5, 2010 at 4:52 PM, <wckwon@xxxxxxxxxxxxx> wrote:
Dear all,

Have you ever tried to simulate 64 cores on Gems 2.1.1 ( ruby loaded ) with Simics 3.0 in MOESI_CMP_directory or MOESI_CMP_token?

For me, it goes well with 16 cores. When I try 64 cores, I get the following kind of cache transition errors continually.

----------------------------------------------------------------------------
successful installation of the ruby timing model.
### Executing "ruby0.init"
Ruby Timing Mode
Creating event queue...
Creating event queue done
Creating system...
 Processors: 64
Creating system done
Ruby initialization complete
Queue registration cpu0
successful installation of the opal queue.
hfa_init_local done:
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:563: m_id is 0
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:563: m_id is 0
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:564: m_version is 16
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:564: m_version is 16
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:565: g_eventQueue_ptr->getTime() is 304
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:565: g_eventQueue_ptr->getTime() is 304
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:566: addr is [0x3f8000c0, line 0x3f8000c0]
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:566: addr is [0x3f8000c0, line 0x3f8000c0]
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:567: event is Fwd_GETS
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:567: event is Fwd_GETS
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:568: state is IS
Warning: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:568: state is IS
Fatal Error: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:569: Invalid transition
Fatal Error: in fn TransitionResult L1Cache_Controller::doTransitionWorker(L1Cache_Event, L1Cache_State, L1Cache_State&, const Address&) in generated/MOESI_CMP_directory/L1Cache_Transitions.C:569: Invalid transition
Abort (SIGABRT) in main thread
The simulation state has been corrupted. Simulation cannot continue.
Please restart Simics.

Thanks,
Woo Cheol

_______________________________________________
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.


[← Prev in Thread] Current Thread [Next in Thread→]