Collect CUDA logs from FluidMark
Closed this issue · 1 comments
vosen commented
Expected outcome:
We can use zluda_dump to fully log CUDA interactions in FluidMark. Output directory contains both log.txt with host-side interactions and all source PTX files
Comments:
zluda_dumpin theory should already support everything that's necessary, but we need someone to actually come test it. This is for 32 bit and we basically never build or test 32 bit- When building for 32 bit build just minimum required (instead of using
cargo xtaskbuild withcargo build -p zluda_inject -p zluda_redirect -p zluda_dump. Ifzluda_dumpfails due toptxfeel free to throw awayptxin 32 bit, it's unnecessary anyway. - It's not a the complete list, but things that might be wrong/broken:
- Some Dark API might unmapped
- x86 Dark API thunk might be wrong
- There might be casts in the source code that assume that pointers are 32 bit. Unlikely in the general code, likely in the compiler (which you don't need in 32 bits). Might be present in bindgenned-bindings, in which case it will require fixing
I can do Dark API - related fixes if needed