Closed
Description
Describe the bug
On the 2.x branch, omniperf profile and the kernel filtering -k option is not limiting the kernels that are being profiled. After running omniperf analyze all kernels are still present. This is needed for applications with many, many kernels and dispatches. The kernel filtering -k option does work as expected for omniperf analyze.
Development Environment:
- Linux Distribution: RHEL/8.9 (TOSS)
- Omniperf Version: 2.0.0-RC1 (6222138)
- GPU: MI300A
- Cluster (if applicable): LLNL System
To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/ROCm/HIP-Examples.git
cd HIP-Examples/add4
./buildit.sh
ROCPROF=${ROCM_PATH}/bin/rocprofv2 omniperf profile -n add4_test -k "add" -- ./gpu-stream-hip
omniperf analyze -p workloads/add4_test/MI300A_A1
# All kernels present in Top Stats and all metrics are essentially the same without any filtering for `omniperf profile`.
Expected behavior
omniperf profile and -k is expected to not collect information on kernels not passed to the flag.