Re: [PATCH] perf tool: Fix symbol offset computation for some dsos

From: Arnaldo Carvalho de Melo
Date: Mon Jul 29 2013 - 16:24:59 EST

Em Sun, Jul 28, 2013 at 09:48:32AM -0600, David Ahern escreveu:
> For some dsos (e.g., libc, libpthread, kernel modules) the symbol offset
> is huge. e.g.,
> qemu-kvm 17238/17242 [007] 762235.640311:
> ffffffff816288a1 __schedule+0x451 ([kernel.kallsyms])
> ffffffff81629609 schedule+0x29 ([kernel.kallsyms])
> ffffffffa00a6ded kvm_vcpu_block+0xffffffffa00a106d (/lib/modules/3.11.0-rc1+/kernel/arch/x86/kvm/kvm.ko)
> ffffffffa00bae6b kvm_arch_vcpu_ioctl_run+0xffffffffa00a118b (/lib/modules/3.11.0-rc1+/kernel/arch/x86/kvm/kvm.ko)
> ffffffffa00a4d7a kvm_vcpu_ioctl+0xffffffffa00a141a (/lib/modules/3.11.0-rc1+/kernel/arch/x86/kvm/kvm.ko)
> ffffffff811a7bdb do_vfs_ioctl+0x8b ([kernel.kallsyms])
> ffffffff811a80c1 sys_ioctl+0x91 ([kernel.kallsyms])
> ffffffff81633182 system_call+0x72 ([kernel.kallsyms])
> 7f882a97af27 __GI___ioctl+0x7f882a891007 (/lib64/
> 100000002 [unknown] ([unknown])
> It seems to be maps with a non-0 start. Taking that into account the
> offsets are correct:

Humm, first reaction is that this should be solved by using one of the
->map/->unmap methods, no?

- Arnaldo
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at