Hi Matt S, Here's the info you requested.
Linux uname -a Linux xxxxxconfidentialxxxxx.com 3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux HIP_PLATFORM Found this below. Is it used by docker ? gem5/util/dockerfiles/gcn-gpu/Dockerfile: -DHIP_COMPILER=clang -DHIP_PLATFORM=rocclr -DCMAKE_PREFIX_PATH="/opt/rocm"\ David From: Matt Sinclair <sincl...@cs.wisc.edu> Sent: Tuesday, April 12, 2022 10:11 AM To: David Fong <da...@chronostech.com>; gem5 users mailing list <gem5-users@gem5.org>; Kyle Roarty <kroa...@wisc.edu> Cc: Poremba, Matthew <matthew.pore...@amd.com> Subject: RE: Error when running test_bwd_bn test In general, yes, MIOpen is less optimized for APUs. I do not recall seeing this before for bwd_bn though. @Kyle Roarty<mailto:kroa...@wisc.edu>: have you seen this? I'm wondering if something is missing with how we set HIP_PLATFORM in the docker? I did some quick digging and it appears to be coming from here: https://github.com/ROCmSoftwarePlatform/MIOpen/blob/rocm-4.0.x/src/ocl/gcn_asm_utils.cpp#L144<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ROCmSoftwarePlatform_MIOpen_blob_rocm-2D4.0.x_src_ocl_gcn-5Fasm-5Futils.cpp-23L144&d=DwMFAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=OkH-8nM02VdNPRt_miVO36vI9580zW1SgNQ4MzWRfqc&m=h1SwgLMRI3CgOTTRaXphol_HtdPq2xNGPYLECiKMfkQ&s=PeviGTnBCGjbDxcb9dROSYb86B-O-fIDWktX03LHPD8&e=> David, what OS are you running this on? In theory since you're using the docker, I wouldn't expect it to matter, but unless Kyle is also seeing this, that print appears to be happening when MIOpen doesn't think you are running on Linux. Or that somewhere in your setup you set the compiler to something other than HCC/clang/rocclr? What is HIP_PLATFORM set to in your setup? Matt From: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Sent: Tuesday, April 12, 2022 10:53 AM To: Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>>; gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Cc: Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>>; Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>> Subject: RE: Error when running test_bwd_bn test Hi Matt S, I'm using gfx801. It proceeds and does not error out. So it just means it's less optimized running with the APU. I don't get this message for my other 3 tests (test_fwd_softmax, test_bwd_softmax, test_fwd_pool), only for test_bwd_bn. I guess there's some special function used in test_bwd_bn that is better optimized in GPU. David From: Matt Sinclair <sincl...@cs.wisc.edu<mailto:sincl...@cs.wisc.edu>> Sent: Monday, April 11, 2022 6:00 PM To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Cc: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>>; Kyle Roarty <kroa...@wisc.edu<mailto:kroa...@wisc.edu>>; Poremba, Matthew <matthew.pore...@amd.com<mailto:matthew.pore...@amd.com>> Subject: RE: Error when running test_bwd_bn test Hi David, My guess is you are using gfx801 for this? If so, does the application actually error out at this point, or just proceed beyond it? If it's the latter, my guess is MIOpen is just complaining that you're running with an APU, which is less well optimized for. If it's the former, then there may be something else in your setup we need to check. Matt From: David Fong via gem5-users <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Sent: Monday, April 11, 2022 1:29 PM To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Cc: David Fong <da...@chronostech.com<mailto:da...@chronostech.com>> Subject: [gem5-users] Error when running test_bwd_bn test Hi, When I run the DNNMark test_bwd_bn, 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 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py --num-compute-units 128 -n3 --gpu-to-dir-latency 120 --TCC_latency 16 --benchmark-root=gem5/gem5-resources/src/gpu/DNNMark/build/benchmarks/test_bwd_bn -c dnnmark_test_bwd_bn --options="-config gem5/gem5-resources/src/gpu/DNNMark/config_example/bn_config.dnnmark -mmap gem5/gem5-resources/src/gpu/DNNMark/mmap.bin" I get this error: MIOpen(HIP): Error [ValidateGcnAssemblerImpl] Specified assembler does not support AMDGPU. Expect performance degradation. Does this mean the test will not run properly with AMD GPU and I should ignore this test? Or the AMD CPU will be doing the computations and it means the test will take longer to complete? David Log for lines before and after the error. build/GCN3_X86/arch/generic/debugfaults.hh:145: warn: MOVNTDQ: Ignoring non-temporal hint, modeling as cacheable! build/GCN3_X86/arch/x86/generated/exec-ns.cc.inc:27: warn: instruction 'frndint' unimplemented build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/GCN3_X86/sim/mem_state.cc:443: info: Increasing stack size by one page. build/GCN3_X86/gpu-compute/gpu_compute_driver.cc:704: warn: unimplemented ioctl: AMDKFD_IOC_ACQUIRE_VM build/GCN3_X86/sim/syscall_emul.hh:1862: warn: mmap: writing to shared mmap region is currently unsupported. The write succeeds on the target, but it will not be propagated to the host or shared mappings build/GCN3_X86/gpu-compute/gpu_compute_driver.cc:455: warn: Signal events are only supported currently build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/GCN3_X86/sim/power_state.cc:105: warn: PowerState: Already in the requested power state, request ignored build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall set_robust_list(...) build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...) build/GCN3_X86/gpu-compute/gpu_compute_driver.cc:599: warn: unimplemented ioctl: AMDKFD_IOC_SET_SCRATCH_BACKING_VA build/GCN3_X86/gpu-compute/gpu_compute_driver.cc:609: warn: unimplemented ioctl: AMDKFD_IOC_SET_TRAP_HANDLER build/GCN3_X86/sim/syscall_emul.hh:2081: warn: prlimit: unimplemented resource 7 build/GCN3_X86/sim/syscall_emul.hh:2081: warn: prlimit: unimplemented resource 7 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(HIP): Error [ValidateGcnAssemblerImpl] Specified assembler does not support AMDGPU. Expect performance degradation. build/GCN3_X86/sim/mem_state.cc:443: info: Increasing stack size by one page. build/GCN3_X86/sim/mem_state.cc:443: info: Increasing stack size by one page. build/GCN3_X86/sim/mem_state.cc:443: info: Increasing stack size by one page. build/GCN3_X86/sim/syscall_emul.cc:683: warn: fcntl: unsupported command 6 build/GCN3_X86/sim/syscall_emul.cc:683: warn: fcntl: unsupported command 6 build/GCN3_X86/sim/syscall_emul.cc:683: warn: fcntl: unsupported command 6
_______________________________________________ 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
