Nazanin,
I have done very similar to what you are trying to do, though my set up had to
be a little bit more complicated because of the requirements of my project.
As you might already know, the cache stuff is all generated from SLICC. You have
to go to the <protocal_name>-dir.sm file, define your module there and whenever
the request is sent down, call your function to find the latency. All that has
to be done in SLICC.
If you explore the SLICC code a little bit, you will find examples of how
external functions are called in SLICC.
--
Nauman
Quoting Nazanin Poorfarhani <nazanin@xxxxxxxxxxxxxx>:
> Hi,
> Our problem is that we are trying to integrate a detailed dram timing
> module into gems. When a request is made to our dram module - it does not
> return a latency number straightaway. The request is instead sent to the
> dram module for processing. The dram model is able to determine the latency
> only after it is done processing the request. At this point the dram
> module can call back the cache hierarchy to inform it of the completion of
> the request and the associated latency.
>
> Does GEMS support what we need at this point? or what extensions are
> needed?
>
> Also Can anybody tell me how or what the cache response latency function
> is?
>
> Thanks,
> Nazanin
>
>
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>
|
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}