[Request Help] I refer the Delegate Debugging document to debug the QLoRA_LLama 3.2-1B model, and want to get the pipeline of linear operation delegation and determine the underlying kernel in XNNPACK #9034
Labels
module: devtools
Issues related to developer tools and code under devtools/
module: xnnpack
Issues related to xnnpack delegation and the code under backends/xnnpack/
triaged
This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Refer the Delegate Debugging document, I have following preparation:
I can get the debug_handle_map in ETRecord file, such as
And also, can get the results same as the document print (https://github.com/pytorch/executorch/blob/main/docs/source/_static/img/print_data_tabular.png)
But current results only are the debug mapping, and I try to use Runtime Logging(event_tracer_start_profiling_delegate, event_tracer_log_profiling_delegate, or ETDumpGen::start_profiling_delegate, ETDumpGen::log_profiling_delegate), it only modified the specific event name in ETDump, for example in XNNExecutor.cpp
So, am I using ExecuTorch delegate debugging incorrectly?
I want to trace a linear operation(such as delegate_debug_identifier=149), get its execution flow in the XNNPACK backend, and determine the underlying XNNPACK execution kernel
cc @digantdesai @mcr229 @cbilgin @Jack-Khuu
The text was updated successfully, but these errors were encountered: