Thanks for the reply!
I'm using MESI_Threee_Level. I checked both develop and stable branches.
Based n what I see, only one prefetcher is created at this line
https://github.com/gem5/gem5/blob/eb919229e63c4daa208a1d9e4856755c1e914154/configs/ruby/MESI_Three_Level.py#L129

Also, by looking at the state machine HTML, I did not see any extra states
for L1 and L2 prefetchers. For example, the variable prefecture is defined
here for L0:
https://github.com/gem5/gem5/blob/eb919229e63c4daa208a1d9e4856755c1e914154/src/mem/ruby/protocol/MESI_Three_Level-L0cache.sm#L49
But I do not see a similar variable for L1 or L2:
https://github.com/gem5/gem5/blob/eb919229e63c4daa208a1d9e4856755c1e914154/src/mem/ruby/protocol/MESI_Three_Level-L1cache.sm#L41

Majid

On Fri, Jul 16, 2021 at 2:50 AM Gabriel Busnot via gem5-users <
gem5-users@gem5.org> wrote:

> Hi Majid,
>
> Which protocol are you using?
> With MESI_Two_Level and MESI_Three_Level, the L1 cache has an
> "enable_prefetch" boolean parameter, juste like the L0.
> You can then customize the prefetcher of each cache according to the
> options available in RubyPrefetcher.py.
>
> Best,
> Gabriel
> _______________________________________________
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to