Replies: 2 comments 1 reply
-
|
Replied to the gist. Backends are selected with environment variables. KFD=1 will use the KFD backend. DEBUG=4 will show tinygrad debugging info. And IOCTL=1 will show you what ioctls it's making. |
Beta Was this translation helpful? Give feedback.
-
|
I added another comment on the Gist with some background about the hang and the work we're doing on that. |
Beta Was this translation helpful? Give feedback.
-
|
@fxkamd, kindly asking if you know of any public documentation on SDMA. I am interested in running indirect buffers (like SDMA_OP_INDIRECT) from SDMA. Is it supposed to work from userspace? What are the fields of SDMA_OP_INDIRECT: priv and csa_addr? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Long time KFD Architect and Linux kernel hacker here. I'm starting to look into the KFD and HSA backends of TinyGrad to help the ongoing debugging effort. I'm trying to get a top-down view of the situation while others are working from the bottom up looking at GPU firmware, drivers and more. I'm drinking from a fire-hose right now.
I shared my initial observations in a gist: https://gist.github.com/fxkamd/ffd02d66a2863e444ec208ea4f3adc48
I'm still working on finding my way around the code base, how the backends are selected, and how the entry points get invoked in the bigger context. Any helpful pointers are appreciated.
Beta Was this translation helpful? Give feedback.
All reactions