The next-gen plugin properly prints errors. This patch improves the
error messages by including the Node-ID of the GPU that failed as well
as a textual representation of the enumeration values.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM
openmp/libomptarget/plugins-nextgen/amdgpu/src/rtl.cpp | ||
---|---|---|
2460 | We could print the fatal message even if hsa_agent_get_info fails, right? We can print the GPU id or unknown/unspecified if the call failed. |
openmp/libomptarget/plugins-nextgen/amdgpu/src/rtl.cpp | ||
---|---|---|
2460 | Yeah, we could probably just initialize it to -1 and continue like nothing happened. |
openmp/libomptarget/plugins-nextgen/amdgpu/src/rtl.cpp | ||
---|---|---|
2460 | That's fine. We have to reinterpret the value as signed, or it will print the uint32_t's maximum value. |
openmp/libomptarget/plugins-nextgen/amdgpu/src/rtl.cpp | ||
---|---|---|
2435 | Is it really possible to have multiple of these hit at a time? |
openmp/libomptarget/plugins-nextgen/amdgpu/src/rtl.cpp | ||
---|---|---|
2435 | Yes, but I think the only one I'm aware of is a typical segfault will present HSA_AMD_MEMORY_FAULT_PAGE_NOT_PRESENT and HSA_AMD_MEMORY_FAULT_READ_ONLY at the same time. |
Is it really possible to have multiple of these hit at a time?