All this code for debugging message enqueueing already exists.
ruby0.debug-verb high
ruby0.debug-filter N (N specifies to debug the Network
component)
ruby0.debug-start-time "1" (where 1 is the cycle to start debugging)
This should emit every message as it is enqueued throughout the
interconnect MessageBuffers
--Mike
Joaquin Sanchez Sanchez wrote:
I have proved the following:
in the GEMS/ruby/network/simple/PerfectSwitch.C file, in the wakeup
function, at the end of it I have added the following code:
m_out[outgoing][vnet]->enqueue(msg_ptr);
cout << "# of cycle: " << g_eventQueue_ptr->getTime() << endl ;
cout << "TYPE OF MESSAGE "<< net_msg_ptr << endl;
cout << "IN MESSAGE SIZE: "<< m_in.size() << endl;
cout << "OUT MESSAGE SIZE: "<< m_out.size() << endl;
cout <<
"---------------------------------------------------------------------------------"
<< endl;
}
But I can solve the problem of knowing the type of the message and who
sends and who receives. Can anyone solve this?
------------------------------------------------------------------------
Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden!
<http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html>.
------------------------------------------------------------------------
_______________________________________________
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.
|