-
Notifications
You must be signed in to change notification settings - Fork 797
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
Can't use perf even compile from source in WSL2 #10829
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
Is there a reason you don't want to use the perf included with the See: #10734 |
Thank you! |
Have the exact same issue. Both
|
The workaround is to run
|
Windows Version
Microsoft Windows [Version 10.0.19045.3693]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
ubuntu20.04
Other Software
No response
Repro Steps
I'm using
Linux version 5.15.133.1-microsoft-standard-WSL2 (root@1c602f52c2e4) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Oct 5 21:02:42 UTC 2023
and havehardwarePerformanceCounters=true
in my.wslconfig
filegit clone --depth=1 https://github.com/microsoft/WSL2-Linux-Kernel.git
build-essential flex bison libssl-dev libelf-dev libbabeltrace-dev libunwind-dev libdw-dev binutils-dev libiberty-dev
WSL2-Linux-Kernel/tools/perf
and make say:sudo ./perf stat -d ls
, unexpectedly got:run
/bin/dmesg | grep -i perf
got
Expected Behavior
Can use perf with all rich features
Actual Behavior
Can't even start it
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: