-
Notifications
You must be signed in to change notification settings - Fork 33
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
'-k' flag does not respect '--max-kernel-num' #187
Labels
bug
Something isn't working
Comments
right now the analyze check is hard-coded here^. I was able to verify that changing the check to >= args.max_kernel_num at least let me see > 10 kernels, but that doesn't address the "expected" behavior |
coleramos425
added a commit
that referenced
this issue
Oct 11, 2023
Signed-off-by: colramos-amd <colramos@amd.com>
Thanks for the suggestion. I agree 100%. I've made the relevant changes and functionality now mirrors that which you outlined in "Expected behavior" |
coleramos425
added a commit
to jasonray/omniperf
that referenced
this issue
Mar 5, 2024
…Cm#187) Signed-off-by: colramos-amd <colramos@amd.com>
coleramos425
added a commit
that referenced
this issue
Mar 5, 2024
* Lock Pandas to version 1.4.3 for tutorial Signed-off-by: colramos-amd <colramos@amd.com> * Establish connection between kernel related flags in Analyze Mode (#187) Signed-off-by: colramos-amd <colramos@amd.com> * Fixing bug in kernel/dispatch filter pytest Signed-off-by: colramos-amd <colramos@amd.com> * More CI logic errors fixed Signed-off-by: colramos-amd <colramos@amd.com> * Update CHANGES Signed-off-by: Cole Ramos <colramos@amd.com> * Update CHANGES Signed-off-by: Cole Ramos <colramos@amd.com> * Update README.md Signed-off-by: Cole Ramos <colramos@amd.com> * bump statman-stopwatch to 2.18 Signed-off-by: Jason Ray <jayray.net@gmail.com> * Fix merge mistakes Signed-off-by: colramos-amd <colramos@amd.com> --------- Signed-off-by: colramos-amd <colramos@amd.com> Signed-off-by: Cole Ramos <colramos@amd.com> Signed-off-by: Jason Ray <jayray.net@gmail.com> Co-authored-by: colramos-amd <colramos@amd.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I want to analyze the 11th most expensive kernel in my application.
First I was confused why
--list-kernels
didn't go past 10, but then I realized there is a--max-kernel-num
option to extend this list.However, even with this applied, I cannot actually select anything past 10 to analyze:
Development Environment:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
IMO, we should:
--list-kernels
option ignore the max kernel number. If a user is asking for the full list of kernels, they probably want the whole thing, and not to see only the top 10.-k 11
), just give it to them (or report that it's out of bounds), rather than limiting it to--max-kernel-num
Essentially
--max-kernel-num
should only be used for expanding the number of kernels under consideration for analyzing and displaying stats over many kernels.The text was updated successfully, but these errors were encountered: