Thanks Kyle for your help. After I created a new directory , downloaded the hsaTopology.py to overwrite previous one, and reran everything I was able to run without MIOpen error.
David Here's a snapshot of the last few lines of the run. And I'm able to view the m5out/stats.txt build/VEGA_X86/gpu-compute/gpu_compute_driver.cc:881: warn: unimplemented ioctl: AMDKFD_IOC_MAP_MEMORY_TO_GPU build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall get_mempolicy(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall madvise(...) build/VEGA_X86/gpu-compute/gpu_compute_driver.cc:881: warn: unimplemented ioctl: AMDKFD_IOC_MAP_MEMORY_TO_GPU build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall get_mempolicy(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall madvise(...) build/VEGA_X86/gpu-compute/gpu_compute_driver.cc:881: warn: unimplemented ioctl: AMDKFD_IOC_MAP_MEMORY_TO_GPU build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall get_mempolicy(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall madvise(...) build/VEGA_X86/gpu-compute/gpu_compute_driver.cc:881: warn: unimplemented ioctl: AMDKFD_IOC_MAP_MEMORY_TO_GPU build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall get_mempolicy(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall madvise(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/gpu-compute/gpu_compute_driver.cc:881: warn: unimplemented ioctl: AMDKFD_IOC_MAP_MEMORY_TO_GPU build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/VEGA_X86/gpu-compute/gpu_compute_driver.cc:881: warn: unimplemented ioctl: AMDKFD_IOC_MAP_MEMORY_TO_GPU build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/VEGA_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) Ticks: 124764978000 Exiting because exiting with last active thread context From: Kyle Roarty <kroa...@wisc.edu> Sent: Friday, March 4, 2022 3:10 PM To: David Fong <da...@chronostech.com>; Poremba, Matthew <matthew.pore...@amd.com>; gem5 users mailing list <gem5-users@gem5.org>; Bobby Bruce <bbr...@ucdavis.edu>; Matt Sinclair <sincl...@cs.wisc.edu> Subject: Re: [gem5-users] Re: gem5 + DGPU (GCN3) build error Vega wasn't setting up the fake filesystem properly, so ROCm was looking for the wrong kernel database file. This led to gem5 needing to do online kernel compilation, which isn't supported. This patch https://gem5-review.googlesource.com/c/public/gem5/+/57309<https://urldefense.proofpoint.com/v2/url?u=https-3A__gem5-2Dreview.googlesource.com_c_public_gem5_-2B_57309&d=DwMF-g&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=OkH-8nM02VdNPRt_miVO36vI9580zW1SgNQ4MzWRfqc&m=7Um0seNUWpUlA6q1j4u_s2vmCC2pLOoVzpb7oViTA6A&s=CgX2V33GxLamNQN2PpinpDVz34Lp2cFJGvixxVZO0Yo&e=> fixes the fake filesystem setup Kyle ________________________________ From: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Sent: Friday, March 4, 2022 12:59 PM To: Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Subject: RE: [gem5-users] Re: gem5 + DGPU (GCN3) build error Hi Matt P., I notice these stat numbers in the overall number for cpu3 (APU). For 40, overall cpu3 (APU) latency numbers are reduced but shaderActiveTicks increased. Do these numbers make sense? David 40 (mem_req_latency, mem_resp_latency) system.cpu3.allLatencyDist::mean 458572.656250 # delay distribution for all (Unspecified) system.cpu3.allLatencyDist::stdev 429452.145064 # delay distribution for all (Unspecified) 50 (mem_req_latency, mem_resp_latency) system.cpu3.allLatencyDist::mean 491744.531250 # delay distribution for all (Unspecified) system.cpu3.allLatencyDist::stdev 439992.936927 # delay distribution for all (Unspecified) Latency is reduced for mean and stdev. 40 (mem_req_latency, mem_resp_latency) system.cpu3.allLatencyDist::overflows 97 1.52% 100.00% # delay distribution for all (Unspecified) system.cpu3.allLatencyDist::min_value 84000 # delay distribution for all (Unspecified) system.cpu3.allLatencyDist::max_value 3796000 # delay distribution for all (Unspecified) 50 (mem_req_latency, mem_resp_latency) system.cpu3.allLatencyDist::overflows 125 1.95% 100.00% # delay distribution for all (Unspecified) system.cpu3.allLatencyDist::min_value 104000 # delay distribution for all (Unspecified) system.cpu3.allLatencyDist::max_value 2651000 # delay distribution for all (Unspecified) 40 (mem_req_latency, mem_resp_latency) system.cpu3.shaderActiveTicks 172369999 # Total ticks that any CU attached to this shader is active (Unspecified) 50 (mem_req_latency, mem_resp_latency) system.cpu3.shaderActiveTicks 171038999 # Total ticks that any CU attached to this shader is active (Unspecified) From: Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>> Sent: Friday, March 4, 2022 10:38 AM To: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Subject: RE: [gem5-users] Re: gem5 + DGPU (GCN3) build error [AMD Official Use Only] Hi David, I generally look at the shader_active_ticks stat for very high level performance comparisons. -Matt From: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Sent: Friday, March 4, 2022 10:27 AM To: Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Subject: RE: [gem5-users] Re: gem5 + DGPU (GCN3) build error [AMD Official Use Only] [CAUTION: External Email] Hi Matt, Thanks for your quick response and support. I'll try the gfx803 (dGPU) first and later the VEGA_X86 version. FYI, I'm trying to adjust a parameter for latency to see stat improvements. gem5/build/GCN3_X86/gpu-compute/GPU.py mem_req_latency = Param.Int(50, "Latency for request from the cu to ruby. "\ "Represents the pipeline to reach the TCP "\ "and specified in GPU clock cycles") mem_resp_latency = Param.Int(50, "Latency for responses from ruby to the "\ "cu. Represents the pipeline between the "\ "TCP and cu as well as TCP data array "\ "access. Specified in GPU clock cycles") Which stat numbers for CUs should I see improvement ? Thanks, David From: Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>> Sent: Friday, March 4, 2022 10:10 AM To: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Subject: RE: [gem5-users] Re: gem5 + DGPU (GCN3) build error [AMD Official Use Only] Hi David, gfx801 is APU (e.g., "Carrizo") and gfx803 is dGPU (e.g., RX 4xx/5xx series). From a gem5 perspective, basically they are setup differently in how memory is laid out. Vega was recently added in 21.2 but from my notes not all of the DNNMark kernels are working and require docker changes to fix. Anyway you can try by generally replacing GCN3_X86 with VEGA_X86 and adding --gfx-version=gfx900 --dgpu to application runs: docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v21-2 scons -sQ -j$(nproc) build/VEGA_X86/gem5.opt docker run --rm -v ${PWD}:${PWD} -v ${PWD}/gem5-resources/src/gpu/DNNMark/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v21-2 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --benchmark-root=gem5-resources/src/gpu/DNNMark/build/benchmarks/test_fwd_softmax -cdnnmark_test_fwd_softmax --options="-config gem5-resources/src/gpu/DNNMark/config_example/softmax_config.dnnmark -mmap gem5-resources/src/gpu/DNNMark/mmap.bin" --gfx-version=gfx900 --dgpu -Matt From: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Sent: Friday, March 4, 2022 10:01 AM To: Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Subject: RE: [gem5-users] Re: gem5 + DGPU (GCN3) build error [AMD Official Use Only] [CAUTION: External Email] Hi Matt, I used gfx801 and it ran ok. What's the difference between gfx801 and gfx803 ? Yes. I'm trying the DGPU flow with VEGA (GCN5). Is this supported for the 21.2.1.0 release with DNNMark? Please send instructions on how to compile and run DNNMark for VEGA. Thanks, David From: Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>> Sent: Friday, March 4, 2022 9:55 AM To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Cc: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Subject: RE: [gem5-users] Re: gem5 + DGPU (GCN3) build error [AMD Official Use Only] Hi, I don't know if this is what is causing this specific forking problem, but gfx900 is VEGA not GCN3. There is a separate build for VEGA. If you want GCN3 dGPU you want gfx803. -Matt From: David Fong via gem5-users <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Sent: Friday, March 4, 2022 9:34 AM To: Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Cc: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Subject: [gem5-users] Re: gem5 + DGPU (GCN3) build error [CAUTION: External Email] Hi Bobby, Thanks for your reply. I tried to rebuild in new directory and rerun same steps. Same results with error. In your regression testing, did you run with the --dgpu" and --gfx-version=gfx900" options? Maybe --dgpu" requires some other code or options? The default flow with APU (no --dgpu, --gfx_version=gfx801) can run DNNMark with no problem. David From: Bobby Bruce <bbr...@ucdavis.edu<mailto:bbr...@ucdavis.edu>> Sent: Thursday, March 3, 2022 6:43 PM To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>; Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>> Cc: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Subject: Re: [gem5-users] gem5 + DGPU (GCN3) build error I think, based on the error I'm seeing here, your build is creating tmp files in the container, which are deleted after DDNMark is built and the docker container is discarded. These are, for some reason, needed in the run and cannot be found. Did you follow the README here for DNNMark and follow it exactly? https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/gpu/DNNMark/<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fnam11.safelinks.protection.outlook.com-5F-2D3Furl-2D3Dhttps-2D253A-2D252F-2D252Furldefense.proofpoint.com-2D252Fv2-2D252Furl-2D253Fu-2D253Dhttps-2D2D3A-2D5F-2D5Fnam11.safelinks.protection.outlook.com-2D5F-2D2D3Furl-2D2D3Dhttps-2D2D253A-2D2D252F-2D2D252Furldefense.proofpoint.com-2D2D252Fv2-2D2D252Furl-2D2D253Fu-2D2D253Dhttps-2D2D2D3A-2D2D5F-2D2D5Fgem5.googlesource.com-2D2D5Fpublic-2D2D5Fgem5-2D2D2D2Dresources-2D2D5F-2D2D2D2B-2D2D5Frefs-2D2D5Fheads-2D2D5Fstable-2D2D5Fsrc-2D2D5Fgpu-2D2D5FDNNMark-2D2D5F-2D2D2526d-2D2D253DDwMFaQ-2D2D2526c-2D2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2D2Dv5A-2D2D5FCdpgnVfiiMM-2D2D2526r-2D2D253DOkH-2D2D2D8nM02VdNPRt-2D2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2D2526m-2D2D253DaBkzz8UWgg6cGJOqO3QnvVOSrQN0fZg7T-2D2D5FjM-2D2D2Df-2D2D2DYQSc-2D2D2526s-2D2D253DwaZIPhDvJYcIbOYvZAGH0pL63ezFEBPqm8wLIJL4QUE-2D2D2526e-2D2D253D-2D2D26data-2D2D3D04-2D2D257C01-2D2D257Cmatthew.poremba-2D2D2540amd.com-2D2D257C88d547e14e03423fd8e808d9fe059fe4-2D2D257C3dd8961fe4884e608e11a82d994e183d-2D2D257C0-2D2D257C0-2D2D257C637820122399508528-2D2D257CUnknown-2D2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D2D253D-2D2D257C3000-2D2D26sdata-2D2D3DJe1WdEqTbYAT66t3ZF1oj7JBgVSVn-2D2D252FFQ2bHmiU6eWqA-2D2D253D-2D2D26reserved-2D2D3D0-2D2526d-2D253DDwMFAg-2D2526c-2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2Dv5A-2D5FCdpgnVfiiMM-2D2526r-2D253DOkH-2D2D8nM02VdNPRt-2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2526m-2D253DCXtsBSeEQThimN8UTcOCBJnofsJFkGT-2D5FC8Ob0g26Nfw-2D2526s-2D253DSZgvV9RNqEIdk8AVGvKhAf2gmSFaCQ655-2D5FCfMRjsjm4-2D2526e-2D253D-2D26data-2D3D04-2D257C01-2D257CMatthew.Poremba-2D2540amd.com-2D257Cbac89e77f805403fc0e308d9fe08edf4-2D257C3dd8961fe4884e608e11a82d994e183d-2D257C0-2D257C0-2D257C637820136584990440-2D257CUnknown-2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D253D-2D257C3000-2D26sdata-2D3DBbNiobevZ97DkSICBTSn0SavOkCdFMlqa>. I admit building and running the GPU code can be tricky as we're heavily dependent on the docker images and things can easily go wrong. Matt or Kyle: do either of you have any idea what's going wrong here? -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fnam11.safelinks.protection.outlook.com-5F-2D3Furl-2D3Dhttps-2D253A-2D252F-2D252Furldefense.proofpoint.com-2D252Fv2-2D252Furl-2D253Fu-2D253Dhttps-2D2D3A-2D5F-2D5Fnam11.safelinks.protection.outlook.com-2D5F-2D2D3Furl-2D2D3Dhttps-2D2D253A-2D2D252F-2D2D252Furldefense.proofpoint.com-2D2D252Fv2-2D2D252Furl-2D2D253Fu-2D2D253Dhttps-2D2D2D3A-2D2D5F-2D2D5Fwww.bobbybruce.net-2D2D2526d-2D2D253DDwMFaQ-2D2D2526c-2D2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2D2Dv5A-2D2D5FCdpgnVfiiMM-2D2D2526r-2D2D253DOkH-2D2D2D8nM02VdNPRt-2D2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2D2526m-2D2D253DaBkzz8UWgg6cGJOqO3QnvVOSrQN0fZg7T-2D2D5FjM-2D2D2Df-2D2D2DYQSc-2D2D2526s-2D2D253DngqE4VS5UTHp-2D2D5FiDKaeA2UgAEOCTJVvsm3o1CfZqeurA-2D2D2526e-2D2D253D-2D2D26data-2D2D3D04-2D2D257C01-2D2D257Cmatthew.poremba-2D2D2540amd.com-2D2D257C88d547e14e03423fd8e808d9fe059fe4-2D2D257C3dd8961fe4884e608e11a82d994e183d-2D2D257C0-2D2D257C0-2D2D257C637820122399508528-2D2D257CUnknown-2D2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D2D253D-2D2D257C3000-2D2D26sdata-2D2D3Dqmxc35H9Rnhwfp8n8qDG-2D2D252FVeT3qIR1UgFT4QSpnLXNeQ-2D2D253D-2D2D26reserved-2D2D3D0-2D2526d-2D253DDwMFAg-2D2526c-2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2Dv5A-2D5FCdpgnVfiiMM-2D2526r-2D253DOkH-2D2D8nM02VdNPRt-2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2526m-2D253DCXtsBSeEQThimN8UTcOCBJnofsJFkGT-2D5FC8Ob0g26Nfw-2D2526s-2D253DAZ8wTwP2SSMwW64B6t4bEawT5GGSIIplivSBTk9Tuhg-2D2526e-2D253D-2D26data-2D3D04-2D257C01-2D257CMatthew.Poremba-2D2540amd.com-2D257Cbac89e77f805403fc0e308d9fe08edf4-2D257C3dd8961fe4884e608e11a82d994e183d-2D257C0-2D257C0-2D257C637820136584990440-2D257CUnknown-2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D253D-2D257C3000-2D26sdata-2D3Db6nM8awXzErkAMFThTud6JPn3O3Mml9tky4NVwXyIEw-2D253D-2D26reserved-2D3D0-2526d-253DDwMFAg-2526c-253DeuGZstcaTDllvimEN8b7jXrwqOf-2Dv5A-5FCdpgnVfiiMM-2526r-253DOkH-2D8nM02VdN> On Wed, Mar 2, 2022 at 4:46 PM David Fong via gem5-users <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> wrote: Hi, I built gem5 + DGPU (GCN3) (gfx900) and ran DNNMark with this command-line [gem5-resources] docker run --rm -v ${PWD}:${PWD} -v${PWD}/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v21-2<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fnam11.safelinks.protection.outlook.com-5F-2D3Furl-2D3Dhttps-2D253A-2D252F-2D252Furldefense.proofpoint.com-2D252Fv2-2D252Furl-2D253Fu-2D253Dhttps-2D2D3A-2D5F-2D5Fnam11.safelinks.protection.outlook.com-2D5F-2D2D3Furl-2D2D3Dhttps-2D2D253A-2D2D252F-2D2D252Furldefense.proofpoint.com-2D2D252Fv2-2D2D252Furl-2D2D253Fu-2D2D253Dhttp-2D2D2D3A-2D2D5F-2D2D5Fgcr.io-2D2D5Fgem5-2D2D2D2Dtest-2D2D5Fgcn-2D2D2D2Dgpu-2D2D2D3Av21-2D2D2D2D2-2D2D2526d-2D2D253DDwMFaQ-2D2D2526c-2D2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2D2Dv5A-2D2D5FCdpgnVfiiMM-2D2D2526r-2D2D253DOkH-2D2D2D8nM02VdNPRt-2D2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2D2526m-2D2D253DaBkzz8UWgg6cGJOqO3QnvVOSrQN0fZg7T-2D2D5FjM-2D2D2Df-2D2D2DYQSc-2D2D2526s-2D2D253D-2D2D2Dkc-2D2D2DQcX1EFLM1qzhO2OMnmlH1P1Vx-2D2D5Fl9s786ttKmXBY-2D2D2526e-2D2D253D-2D2D26data-2D2D3D04-2D2D257C01-2D2D257Cmatthew.poremba-2D2D2540amd.com-2D2D257C88d547e14e03423fd8e808d9fe059fe4-2D2D257C3dd8961fe4884e608e11a82d994e183d-2D2D257C0-2D2D257C0-2D2D257C637820122399508528-2D2D257CUnknown-2D2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D2D253D-2D2D257C3000-2D2D26sdata-2D2D3DAO0DKhD-2D2D252B6XYPMJe0Ih-2D2D252B-2D2D252BX4fPZ9moDpbh5Fk6gqEx-2D2D252BGk-2D2D253D-2D2D26reserved-2D2D3D0-2D2526d-2D253DDwMFAg-2D2526c-2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2Dv5A-2D5FCdpgnVfiiMM-2D2526r-2D253DOkH-2D2D8nM02VdNPRt-2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2526m-2D253DCXtsBSeEQThimN8UTcOCBJnofsJFkGT-2D5FC8Ob0g26Nfw-2D2526s-2D253D5YUX5eszYu3C84b-2D5FRm3pYiVJA8asGwZOtdUpR-2D2D0k9Tk-2D2526e-2D253D-2D26data-2D3D04-2D257C01-2D257CMatthew.Poremba-2D2540amd.com-2D257Cbac89e77f805403fc0e308d9fe08edf4-2D257C3dd8961fe4884e608e11a82d994e183d-2D257C0-2D257C0-2D257C637820136584990440-2D257CUnknown-2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D253D-2D257C3000-2D26sdata-2D3Dz7TBx4qC3pbO2rUt6hI-2D252FaEVbRtJRUNSoqlz03Gwn-2D252Bq8-2D253D-2D26res> python3 generate_cachefiles.py cachefiles.csv --gfx-version=gfx900 --num-cus=4 [gem5-gpu-dnn] docker run --rm -v ${PWD}:${PWD} -v ${PWD}/gem5/gem5-resources/src/gpu/DNNMark/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v21-2<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fnam11.safelinks.protection.outlook.com-5F-2D3Furl-2D3Dhttps-2D253A-2D252F-2D252Furldefense.proofpoint.com-2D252Fv2-2D252Furl-2D253Fu-2D253Dhttps-2D2D3A-2D5F-2D5Fnam11.safelinks.protection.outlook.com-2D5F-2D2D3Furl-2D2D3Dhttps-2D2D253A-2D2D252F-2D2D252Furldefense.proofpoint.com-2D2D252Fv2-2D2D252Furl-2D2D253Fu-2D2D253Dhttp-2D2D2D3A-2D2D5F-2D2D5Fgcr.io-2D2D5Fgem5-2D2D2D2Dtest-2D2D5Fgcn-2D2D2D2Dgpu-2D2D2D3Av21-2D2D2D2D2-2D2D2526d-2D2D253DDwMFaQ-2D2D2526c-2D2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2D2Dv5A-2D2D5FCdpgnVfiiMM-2D2D2526r-2D2D253DOkH-2D2D2D8nM02VdNPRt-2D2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2D2526m-2D2D253DaBkzz8UWgg6cGJOqO3QnvVOSrQN0fZg7T-2D2D5FjM-2D2D2Df-2D2D2DYQSc-2D2D2526s-2D2D253D-2D2D2Dkc-2D2D2DQcX1EFLM1qzhO2OMnmlH1P1Vx-2D2D5Fl9s786ttKmXBY-2D2D2526e-2D2D253D-2D2D26data-2D2D3D04-2D2D257C01-2D2D257Cmatthew.poremba-2D2D2540amd.com-2D2D257C88d547e14e03423fd8e808d9fe059fe4-2D2D257C3dd8961fe4884e608e11a82d994e183d-2D2D257C0-2D2D257C0-2D2D257C637820122399508528-2D2D257CUnknown-2D2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D2D253D-2D2D257C3000-2D2D26sdata-2D2D3DAO0DKhD-2D2D252B6XYPMJe0Ih-2D2D252B-2D2D252BX4fPZ9moDpbh5Fk6gqEx-2D2D252BGk-2D2D253D-2D2D26reserved-2D2D3D0-2D2526d-2D253DDwMFAg-2D2526c-2D253DeuGZstcaTDllvimEN8b7jXrwqOf-2D2Dv5A-2D5FCdpgnVfiiMM-2D2526r-2D253DOkH-2D2D8nM02VdNPRt-2D5FmiVO36vI9580zW1SgNQ4MzWRfqc-2D2526m-2D253DCXtsBSeEQThimN8UTcOCBJnofsJFkGT-2D5FC8Ob0g26Nfw-2D2526s-2D253D5YUX5eszYu3C84b-2D5FRm3pYiVJA8asGwZOtdUpR-2D2D0k9Tk-2D2526e-2D253D-2D26data-2D3D04-2D257C01-2D257CMatthew.Poremba-2D2540amd.com-2D257Cbac89e77f805403fc0e308d9fe08edf4-2D257C3dd8961fe4884e608e11a82d994e183d-2D257C0-2D257C0-2D257C637820136584990440-2D257CUnknown-2D257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0-2D253D-2D257C3000-2D26sdata-2D3Dz7TBx4qC3pbO2rUt6hI-2D252FaEVbRtJRUNSoqlz03Gwn-2D252Bq8-2D253D-2D26res> gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py --dgpu --gfx-version=gfx900 -n3 --benchmark-root=gem5/gem5-resources/src/gpu/DNNMark/build/benchmarks/test_fwd_softmax -cdnnmark_test_fwd_softmax --options="-config gem5/gem5-resources/src/gpu/DNNMark/config_example/softmax_config.dnnmark -mmap gem5/gem5-resources/src/gpu/DNNMark/mmap.bin" and got this error message : build/GCN3_X86/sim/syscall_emul.cc:683: warn: fcntl: unsupported command 6 build/GCN3_X86/sim/mem_state.cc:443: info: Increasing stack size by one page. build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) sh: 1: Cannot fork MIOpen Error: /root/driver/MLOpen/src/hipoc/hipoc_program.cpp:195: Cant find file: /tmp/miopen-MIOpenSoftmax.cl-9c04-5b2f-4076-0450/MIOpenSoftmax.cl.o build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mbind(...) MIOpen Error: 7 at /home/dfong/work/ext_ips/gem5-gpu-dnn/gem5/gem5-resources/src/gpu/DNNMark/core/include/dnn_wrapper.h485Ticks: 571357584000 Exiting because exiting with last active thread context Am I missing a step in compilation process or some other settings ? Thanks, David _______________________________________________ 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
