[gem5-users] Re: GEM5/Ruby and MESI_Three_Level protocol
Hello Okay. I had not realised that some of the files were shared between MESI_Three_Level and MESI_Two_Level. That would explain why MESI_Three_level is comiling okay. Tks for the pointer. Best regards J.Osmany From: Shehab Elsayed [mailto:shehaby...@gmail.com] Sent: 28 May 2020 16:49 To: gem5 users mailing list Cc: Javed Osmany Subject: Re: [gem5-users] GEM5/Ruby and MESI_Three_Level protocol Which files do you think are missing? There are some shared files between MESI_Three_Level and MESI_Two-Level such as the L2 controller. You can find a list of all files used by the MESI_Three_Level protocol in src/mem/ruby/protocol/MESI_Three_Level.slicc. I hope this helps. On Thu, May 28, 2020 at 11:37 AM Javed Osmany via gem5-users mailto:gem5-users@gem5.org>> wrote: Hello 1. I am able to successfully generate the executable gem5 simulator for [ARM ISA, MESI_Three_Level protocol]. The command I used being: a. scons -j4 build/ARM_MESI_3_level/gem5.opt --default=ARM PROTOCOL=MESI_Three_Level SLICC_HTML=True 2. Also, I am able successfully generate the executable gem5 simulator for [X86 ISA, MESI_Three_Level protocol]. The command I used being: a. scons -j4 build/X86_MESI_3_level/gem5.opt --default=X86 PROTOCOL=MESI_Three_Level SLICC_HTML=True However, if I look in src/mem/ruby/protocol, the code for MESI_Three_Level is as follows: [j00533938@lhrplinux1 protocol]$ ll MESI_Three_Level* -rw-rw-r-- 1 j00533938 j00533938 40031 May 28 09:17 MESI_Three_Level-L0cache.sm -rw-rw-r-- 1 j00533938 j00533938 36841 May 28 09:17 MESI_Three_Level-L1cache.sm -rw-rw-r-- 1 j00533938 j00533938 4270 May 28 09:17 MESI_Three_Level-msg.sm -rw-rw-r-- 1 j00533938 j00533938 316 Mar 20 17:42 MESI_Three_Level.slicc Therefore, it looks to me that the code for MESI_Three_Level is not complete. Thus it is not clear to me how the executable gem5 simulator for MESI_Three_Level is being generated. Any thoughts on this please? Thanks in advance. JO ___ gem5-users mailing list -- gem5-users@gem5.org<mailto:gem5-users@gem5.org> To unsubscribe send an email to gem5-users-le...@gem5.org<mailto: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
[gem5-users] Re: GEM5/Ruby and MESI_Three_Level protocol
Hello, Open the file 'MESI_Three_Level.slicc' and you will see the files the protocol MESI_Three_Level is being generated from. You will see that it is using some components from the MESI_Two_Level protocol. Hope this is helping you. Carlos On 28/5/20 11:48, Javed Osmany via gem5-users wrote: Hello 1.I am able to successfully generate the executable gem5 simulator for [ARM ISA, MESI_Three_Level protocol]. The command I used being: a.scons -j4 build/ARM_MESI_3_level/gem5.opt --default=ARM PROTOCOL=MESI_Three_Level SLICC_HTML=True 2.Also, I am able successfully generate the executable gem5 simulator for [X86 ISA, MESI_Three_Level protocol]. The command I used being: a.scons -j4 build/X86_MESI_3_level/gem5.opt --default=X86 PROTOCOL=MESI_Three_Level SLICC_HTML=True However, if I look in src/mem/ruby/protocol, the code for MESI_Three_Level is as follows: [j00533938@lhrplinux1 protocol]$ ll MESI_Three_Level* -rw-rw-r-- 1 j00533938 j00533938 40031 May 28 09:17 MESI_Three_Level-L0cache.sm -rw-rw-r-- 1 j00533938 j00533938 36841 May 28 09:17 MESI_Three_Level-L1cache.sm -rw-rw-r-- 1 j00533938 j00533938 4270 May 28 09:17 MESI_Three_Level-msg.sm -rw-rw-r-- 1 j00533938 j00533938 316 Mar 20 17:42 MESI_Three_Level.slicc Therefore, it looks to me that the code for MESI_Three_Level is not complete. Thus it is not clear to me how the executable gem5 simulator for MESI_Three_Level is being generated. Any thoughts on this please? Thanks in advance. JO ___ 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
[gem5-users] Re: GEM5/Ruby and MESI_Three_Level protocol
Which files do you think are missing? There are some shared files between MESI_Three_Level and MESI_Two-Level such as the L2 controller. You can find a list of all files used by the MESI_Three_Level protocol in src/mem/ruby/protocol/MESI_Three_Level.slicc. I hope this helps. On Thu, May 28, 2020 at 11:37 AM Javed Osmany via gem5-users < gem5-users@gem5.org> wrote: > Hello > > > > 1. I am able to successfully generate the executable gem5 simulator > for [ARM ISA, MESI_Three_Level protocol]. The command I used being: > > a. scons -j4 build/ARM_MESI_3_level/gem5.opt --default=ARM > PROTOCOL=MESI_Three_Level SLICC_HTML=True > > > > 2. Also, I am able successfully generate the executable gem5 > simulator for [X86 ISA, MESI_Three_Level protocol]. The command I used > being: > > a. scons -j4 build/X86_MESI_3_level/gem5.opt --default=X86 > PROTOCOL=MESI_Three_Level SLICC_HTML=True > > > > However, if I look in src/mem/ruby/protocol, the code for MESI_Three_Level > is as follows: > > > > [j00533938@lhrplinux1 protocol]$ ll MESI_Three_Level* > > -rw-rw-r-- 1 j00533938 j00533938 40031 May 28 09:17 > MESI_Three_Level-L0cache.sm > > -rw-rw-r-- 1 j00533938 j00533938 36841 May 28 09:17 > MESI_Three_Level-L1cache.sm > > -rw-rw-r-- 1 j00533938 j00533938 4270 May 28 09:17 MESI_Three_Level-msg.sm > > -rw-rw-r-- 1 j00533938 j00533938 316 Mar 20 17:42 MESI_Three_Level.slicc > > > > > > Therefore, it looks to me that the code for MESI_Three_Level is not > complete. Thus it is not clear to me how the executable gem5 simulator for > MESI_Three_Level is being generated. > > > > > > Any thoughts on this please? > > > > Thanks in advance. > > JO > > > ___ > 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
