-
Notifications
You must be signed in to change notification settings - Fork 166
Experiment with trace #2251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experiment with trace #2251
Conversation
| rt = Runtime() | ||
| with rt.sequence(tensor_ty, scalar_ty, tensor_ty) as (A, F, C): | ||
| rt.enable_trace(trace_size) | ||
| rt.enable_trace(trace.numel() * np.dtype(trace.dtype).itemsize) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jackl-xilinx Does enable_trace take the number of bytes?
|
@jackl-xilinx, whenever you have time, could you please try running this? Here is the trace I get too trace.txt. After that we can see how we can get rid of the dummy variable. |
|
Looking at this again, I think we might as well completely hide the tracing. Consider something like: iron.enable_tracing()
# Magically insert the trace at kernel launch and into the RT sequence
vector_scalar_mul(input, factor, output)
iron.stop_tracing("trace.bin") |
|
Better approach is implemented in #2541. Closing this one. |
CoreFunctionis a wrapper around the C++ core code (ignore for now)Notes from the discussion with Jack:
enable_traceneeds to internally figure out that the trace buffer is the last argument. At the moment, it is assumed to be the fifth argument and hence we have this dummy argument at kernel launch.Run with: