Hello Bobby It was our local gitlab repository, where the problem resided.
Tks JO From: Bobby Bruce [mailto:bbr...@ucdavis.edu] Sent: 03 March 2022 22:07 To: gem5 users mailing list <gem5-users@gem5.org> Cc: Javed Osmany <javed.osm...@huawei.com> Subject: Re: [gem5-users] Re: CHI Which gitlab repository was this? I don't believe we maintain one officially. The github repo is a mirror of https://gem5.googlesource.com/public/gem5 so should be up-to-date. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Thu, Mar 3, 2022 at 2:30 AM Javed Osmany via gem5-users <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> wrote: Hello Just an update … Previously I had cloned the latest gem5 version (21.2.1.0) from a gitlab repository (as I was having proxy issues in accessing github). Something must have gone wrong in the cloning, since that was causing the problem with the CHI protocol compilation. I am now able to download the latest gem5 (21.2.1.0) directly from github and am now able to successfully compile it for the CHI protocol. Regards JO From: Javed Osmany Sent: 02 March 2022 15:44 To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Cc: Javed Osmany <javed.osm...@huawei.com<mailto:javed.osm...@huawei.com>> Subject: RE: CHI Hello So I thought the reason why my previous command line options were not being parsed in the latest version of gem5 (21..2.1.0) could be because the CHI.py and CHI_config.py files were not being compiled when generating the executable gem5.opt binary. So I tried the following command: rm -rf build/ARM scons -j4 build/ARM/gem5.opt --default=ARM PROTOCOL=CHI The above command terminates with: Building in /home/j00533938/gitlab/gem5-21.2.1.0/gem5/build/ARM Using saved variables file /home/j00533938/gitlab/gem5-21.2.1.0/gem5/build/variables/ARM scons: *** Invalid value for option PROTOCOL: CHI. Valid values are: ['GPU_VIPER', 'GPU_VIPER_Baseline', 'GPU_VIPER_Region', 'GPU_RfO', 'MOESI_AMD_Base', 'MESI_Two_Level', 'MESI_Three_Level', 'MI_example', 'MOESI_CMP_directory', 'MOESI_CMP_token', 'MOESI_hammer', 'Garnet_standalone', 'None', 'MSI'] Thus it looks like CHI is not supported in this latest version of gem5 ?? So looking in build_opts/ARM we have: j00533938@lhrpbig100002:~/gitlab/gem5-21.2.1.0/gem5/build_opts$<mailto:j00533938@lhrpbig100002:~/gitlab/gem5-21.2.1.0/gem5/build_opts$> more ARM TARGET_ISA = 'arm' CPU_MODELS = 'AtomicSimpleCPU,TimingSimpleCPU,O3CPU,MinorCPU' PROTOCOL = 'MOESI_CMP_directory' Is CHI protocol not supported in the latest gem5 release? Tks in advance JO From: Javed Osmany Sent: 02 March 2022 15:00 To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Cc: Javed Osmany <javed.osm...@huawei.com<mailto:javed.osm...@huawei.com>> Subject: CHI Hello I am using the latest version of gem5 (21.2.1.0). Previously, when using gem5 version 21.0.0.0, in the function “def define_options(parser)” (in CHI.py), I added some command line options as such: def define_options(parser): parser.add_option("--chi-config", action="store", type="string", default=None, help="NoC config. parameters and bindings. " "Required for CustomMesh topology") ## Add command line options specifically for the [Big, Middle, Little] ## Cluster. parser.add_option("--verbose", action="store", type="string", default="false", help="Disable/Enable verbose printing for debugging") parser.add_option("--num-clusters", action="store", type="string", default=0, help="Number of Clusters in the system") I was then able to specify the options when running as: ./build/ARM/gem5.opt --outdir=m5out_parsec_blackscoles_1_clust_little_4_cpu_all_shared_l2 configs/example/se_kiri n_custom.py --ruby --topology=Pt2Pt --cpu-type=DerivO3CPU --num-cpus=4 --num-dirs=1 --num-l3caches=1 --verbose=true --num-clusters=0 ….. This then worked okay. The new command line options I added was recognised okay. Now with gem5 21.2.1.0, I have added the same options to the define_options(parser) function (in CHI.py) as such: def define_options(parser): parser.add_argument("--chi-config", action="store", type=str, default=None, help="NoC config. parameters and bindings. " "Required for CustomMesh topology") ## Add command line options specifically for the [Big, Middle, Little] ## Cluster. parser.add_option("--verbose", action="store", type="string", default="false", help="Disable/Enable verbose printing for debugging") parser.add_option("--num-clusters", action="store", type="string", default=0, help="Number of Clusters in the system") : : But the following command does not work anymore: ./build/ARM/gem5.opt --outdir=m5out_parsec_blackscoles_1_clust_little_4_cpu_all_shared_l2 configs/example/se_kiri n_custom.py --ruby --topology=Pt2Pt --cpu-type=DerivO3CPU --num-cpus=4 --num-dirs=1 --num-l3caches=1 --verbose=true --num-clusters=0 The error message being: command line: ./build/ARM/gem5.opt --outdir=m5out_parsec_blackscoles_1_clust_little_4_cpu_all_shared_l2 configs/example/se_kirin_custom.py --ruby --topology=Pt2Pt --cpu-type=DerivO3CPU --num-cpus=4 --num-dirs=1 --num-l3caches=1 --verbose=true --num-clusters=0 Usage: se_kirin_custom.py [options] se_kirin_custom.py: error: no such option: --verbose Any pointers why the new command line options I had previously specified are now not working? Tks 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
