Date: | Tue, 30 Jan 2007 14:57:44 -0600 |
---|---|
From: | Dan Gibson <degibson@xxxxxxxx> |
Subject: | Re: [Gems-users] non-cacheable memory |
SimicsProcessor.C: It looks something like this: if (m_current_instruction_count != SIMICS_get_insn_count(m_proc)) { clearActiveRequestVector(); m_current_instruction_count = SIMICS_get_insn_count(m_proc); } Regards, Dan Dave Z. wrote: --- Mike Marty <mikem@xxxxxxxxxxx> wrote:If you are not interested in modeling the memorysystem affects of issuinga request to memory, possibly incurringinterconnect delays and etc., thensure, return a fixed number of stall cycles toSimicsThis actually won't work. You first need to stallSimics, then after the stall elapses, Simics will ask again if it can proceed and you need to then return a stall of 0.Where does such an implementation take place in Rubycode (so that I can have an example to take a look)?Thanks Dave____________________________________________________________________________________Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com _______________________________________________ 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. -- http://www.cs.wisc.edu/~gibson [esc]:wq! |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] non-cacheable memory, Dave Z. |
---|---|
Next by Date: | [Gems-users] Problem with ruby compilation, Srinath Sridharan |
Previous by Thread: | Re: [Gems-users] non-cacheable memory, Dave Z. |
Next by Thread: | Re: [Gems-users] non-cacheable memory, Dave Z. |
Indexes: | [Date] [Thread] |