Re: [Gems-users] stall cycles

[Luke Yen <lyen@xxxxxxxxxxx>]

Hello Chris:

  There is no easy way to determine this information by default.  All
source operand stalls are recorded in dynamic.C, through the WAIT_X_STAGE
case statements in Schedule().  If any operands are not ready, the
isReady() call will fail for the corresponding source operand.

   In order to track this information, I recommend that whenever an
instruction stalls due to operands not being ready to lookup waiting
loads in the MSHR (defined in rubycache.C), and to see if any of those
loads are writing to operands this waiting instruction is dependent on.

   Luke

On Wed, 28 Sep 2005, Christian Bienia wrote:

> Hi,
>
> I'd like to figure out how often the pipeline had to be stalled  because
> source operands were unavailable due to uncompleted loads (an
> approximation would suffice). In other words, I need something similar
> to the statistics about the fetch stalls, but for the execution stage.
> Is there a way to determine that from the numbers reported by default?
>
> Thanks guys.
>
> Chris
>
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>