* Arnaldo Carvalho de Melo <a...@kernel.org> wrote:
> Hi Ingo/Thomas,
>
> Please consider pulling,
>
> Best regards,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 4f5cafb5cb8471e54afdc9054d973535614f7675:
>
> Linux 5.4-rc3 (2019-10-13 16:37:36 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-urgent-for-mingo-5.4-20191017
>
> for you to fetch changes up to 1abecfcaa7bba21c9985e0136fa49836164dd8fd:
>
> perf kmem: Fix memory leak in compact_gfp_flags() (2019-10-16 10:08:32
> -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> perf buildid-cache:
>
> Adrian Hunter:
>
> - Fix mode setting in copyfile_mode_ns() when copying /proc/kcore.
>
> perf evlist:
>
> Andi Kleen:
>
> - Fix freeing id arrays.
>
> tools headers:
>
> - Sync sched.h anc kvm.h headers with the kernel sources.
>
> perf jvmti:
>
> Thomas Richter:
>
> - Link against tools/lib/ctype.o to have weak strlcpy().
>
> perf annotate:
>
> Gustavo A. R. Silva:
>
> - Fix multiple memory and file descriptor leaks, found by coverity.
>
> perf c2c/kmem:
>
> Yunfeng Ye:
>
> - Fix leaks in error handling paths in 'perf c2c', 'perf kmem', found by
> internal static analysis tool.
>
> Signed-off-by: Arnaldo Carvalho de Melo <a...@redhat.com>
>
> ----------------------------------------------------------------
> Adrian Hunter (1):
> perf tools: Fix mode setting in copyfile_mode_ns()
>
> Andi Kleen (1):
> perf evlist: Fix fix for freed id arrays
>
> Arnaldo Carvalho de Melo (4):
> tools headers kvm: Sync kvm headers with the kernel sources
> tools headers kvm: Sync kvm headers with the kernel sources
> tools headers kvm: Sync kvm.h headers with the kernel sources
> tools headers UAPI: Sync sched.h with the kernel
>
> Gustavo A. R. Silva (1):
> perf annotate: Fix multiple memory and file descriptor leaks
>
> Thomas Richter (1):
> perf jvmti: Link against tools/lib/ctype.h to have weak strlcpy()
>
> Yunfeng Ye (3):
> perf tools: Fix resource leak of closedir() on the error paths
> perf c2c: Fix memory leak in build_cl_output()
> perf kmem: Fix memory leak in compact_gfp_flags()
>
> tools/arch/x86/include/uapi/asm/svm.h | 1 +
> tools/arch/x86/include/uapi/asm/vmx.h | 6 +++++-
> tools/include/uapi/linux/kvm.h | 2 ++
> tools/include/uapi/linux/sched.h | 30 ++++++++++++++++++++++++++++--
> tools/perf/builtin-c2c.c | 14 +++++++++-----
> tools/perf/builtin-kmem.c | 1 +
> tools/perf/jvmti/Build | 6 +++++-
> tools/perf/util/annotate.c | 2 +-
> tools/perf/util/copyfile.c | 8 +++++---
> tools/perf/util/evlist.c | 2 +-
> tools/perf/util/header.c | 4 +++-
> tools/perf/util/util.c | 6 ++++--
> 12 files changed, 65 insertions(+), 17 deletions(-)
Pulled, thanks a lot Arnaldo!
A minor bugreport:
There's a new nuisance message that I noticed when 'perf top' is started:
a "vmlinux file has not been found" - with a "press any key" - but the
message doesn't actually wait for the keypress, it's cleared on the first
screen refresh...
I'd argue that both the keypress action and the warning message is
superfluous:
- It annoys users while not actually giving any straightforward way to
fix it. It's displayed on every startup of perf top, which is highly
distracting.
- At least on Ubuntu it appears to be wrong, because the vmlinux is
available and symbol resolution/annotation appears to be working fine:
# uname -a
Linux dagon 5.4.0-rc3-custom-00557-gb6c81ae120e0 #1 SMP PREEMPT Sun Oct
20 15:28:00 CEST 2019 x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l | grep gb6c81ae120e
ii linux-headers-5.4.0-rc3-custom-00557-gb6c81ae120e0
5.4.0-rc3-custom-00557-gb6c81ae120e0-1 amd64 Linux
kernel headers for 5.4.0-rc3-custom-00557-gb6c81ae120e0 on amd64
ii linux-image-5.4.0-rc3-custom-00557-gb6c81ae120e0
5.4.0-rc3-custom-00557-gb6c81ae120e0-1 amd64 Linux
kernel, version 5.4.0-rc3-custom-00557-gb6c81ae120e0
ii linux-image-5.4.0-rc3-custom-00557-gb6c81ae120e0-dbg
5.4.0-rc3-custom-00557-gb6c81ae120e0-1 amd64 Linux
kernel debugging symbols for 5.4.0-rc3-custom-00557-gb6c81ae120e0
ii linux-libc-dev:amd64
5.4.0-rc3-custom-00557-gb6c81ae120e0-1 amd64 Linux
support headers for userspace development
Note that the 'dbg' package is installed which includes the vmlinux,
and perf does seem to find it:
# dpkg-query -L linux-image-5.4.0-rc3-custom-00557-gb6c81ae120e0-dbg |
grep vmlinux$
/usr/lib/debug/lib/modules/5.4.0-rc3-custom-00557-gb6c81ae120e0/vmlinux
I can see annotated kernel functions just fine.
- Finally, when I run perf as root then kallsyms and /proc/kcore is used
to annotate the kernel. So the 'cannot resolve' message cannot even be
true. :-)
Instead I believe some sort of explanation should be printed in the
natural flow when there's an unknown symbol or someone tries to enter a
kernel symbol that cannot be further resolved. Even there it probably
shouldn't be a 'warning' message, but something printed in-line where
usually we'd see the annotated output - to disrupt the normal workflow as
little as possible.
Secondly, there also appears to be a TUI weirdness when the annotated
kernel functions are small (or weird): the blue cursor is stuck at the
top and I cannot move between the annotated instructions with the down/up
arrow:
Samples: 13M of event 'cycles', 4000 Hz, Event count (approx.): 1272420588851
clear_page_rep
/usr/lib/debug/boot/vmlinux-5.4.0-rc3-custom-00557-gb6c81ae120e0 [Percent:
local period]
0.01 │ mov $0x200,%ecx
▒
│ xorl %eax,%eax
▒
0.01 │ xor %eax,%eax
▒
│ rep stosq
▒
99.27 │ rep stos %rax,%es:(%rdi)
▒
│ ret
▒
0.71 │ ← retq
I can still exit the screen with 'q', and can move around in larger
annotated kernel functions. Not sure whether it's related to function
size, or perhaps to the 'hottest' instruction that the cursor is normally
placed at.
Thanks,
Ingo
