Date: | Tue, 26 Sep 2006 09:38:43 -0500 (CDT) |
---|---|
From: | Luke Yen <lyen@xxxxxxxxxxx> |
Subject: | Re: [Gems-users] Understanding opal scheduling |
Hi Aniket, The ROB entry availability is checked in pseq.C's fetchInstSimple() function, during the fetch loop. Grep for PSEQ_FETCH_WIN_FULL for the stalling instance. Opal assumes an infinite load and store queue. Therefore the front-end is never stalled due to LSQ reaching max capacity. However, there is a warning printed out when the LSQ reaches 2x the ROB size to let you know something has gone awry. I recommend creating your own PSEQ_FETCH_LSQ_FULL flag to simulate a front-end stall for a finite-sized LSQ. Luke |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] Simics and Ruby parameters, Daniele Bordes |
---|---|
Next by Date: | Re: [Gems-users] Simics + Ruby slowdown, Daniele Bordes |
Previous by Thread: | [Gems-users] Understanding opal scheduling, Aniket Dilip Naik |
Next by Thread: | [Gems-users] Understand the protocol trace, Lei Yang |
Indexes: | [Date] [Thread] |