perf_event: fix getting symbol error if kernel is relocatable
Subsystems (2)
cover perf_event: fix getting symbol error if kernel is relocatable
Hi,
If the kernel is relocatable, perf tools can't get symbol name correctly, See: http://lkml.org/lkml/2009/12/20/218
The purpose of this patchset is to fix this bug, and it base on my previously patchset: http://lkml.org/lkml/2009/12/29/4
since it used 'inject' event
arch/x86/boot/compressed/head_32.S | 2 ++ arch/x86/boot/compressed/head_64.S | 3 +++ arch/x86/include/asm/bootparam.h | 3 ++- arch/x86/kernel/asm-offsets_32.c | 1 + arch/x86/kernel/asm-offsets_64.c | 1 + arch/x86/kernel/cpu/perf_event.c | 10 ++++++++++ include/linux/perf_event.h | 1 + kernel/perf_event.c | 23 +++++++++++++++++++++-- tools/perf/builtin-record.c | 3 +++ tools/perf/util/session.c | 6 ++++++ tools/perf/util/symbol.c | 13 +++++++++++++ tools/perf/util/symbol.h | 3 ++- 12 files changed, 65 insertions(+), 4 deletions(-)
PATCH 1/3 x86: record relocation offset
Record relocation offset, perf tools will use it
to adjust kernel symbol address
--- arch/x86/boot/compressed/head_32.S | 2 ++ arch/x86/boot/compressed/head_64.S | 3 +++ arch/x86/include/asm/bootparam.h | 3 ++- arch/x86/kernel/asm-offsets_32.c | 1 + arch/x86/kernel/asm-offsets_64.c | 1 + arch/x86/kernel/cpu/perf_event.c | 4 ++++ 6 files changed, 13 insertions(+), 1 deletions(-)
arch/x86/boot/compressed/head_32.S +2 -0
@@ -151,6 +151,8 @@ relocated: movl %ebp, %ebx subl $LOAD_PHYSICAL_ADDR, %ebx jz 2f /* Nothing to be done if loaded at compiled addr. */ + + movl %ebx, BP_relocate_offset(%esi) /* * Process relocations. */
arch/x86/boot/compressed/head_64.S +3 -0
@@ -90,6 +90,9 @@ ENTRY(startup_32) addl %eax, %ebx notl %eax andl %eax, %ebx + movl %ebx, %eax + subl $LOAD_PHYSICAL_ADDR, %eax + movl %eax, BP_relocate_offset(%esi) #else movl $LOAD_PHYSICAL_ADDR, %ebx #endif
arch/x86/include/asm/bootparam.h +2 -1
@@ -88,7 +88,8 @@ struct boot_params {__u8 _pad2[4 ];/* 0x054 */ __u64 tboot_addr;/* 0x058 */ struct ist_info ist_info;/* 0x060 */ -__u8 _pad3[16 ];/* 0x070 */ +__s32 relocate_offset;/* 0x070 */ +__u8 _pad3[12 ];/* 0x074 */ __u8 hd0_info[16 ];/* obsolete! */ /* 0x080 */ __u8 hd1_info[16 ];/* obsolete! */ /* 0x090 */ struct sys_desc_table sys_desc_table;/* 0x0a0 */
arch/x86/kernel/asm-offsets_32.c +1 -0
@@ -148,4 +148,5 @@ void foo(void)OFFSET (BP_hardware_subarch, boot_params, hdr.hardware_subarch);OFFSET (BP_version, boot_params, hdr.version);OFFSET (BP_kernel_alignment, boot_params, hdr.kernel_alignment); +OFFSET (BP_relocate_offset, boot_params, relocate_offset); }
arch/x86/kernel/asm-offsets_64.c +1 -0
@@ -127,6 +127,7 @@ int main(void)OFFSET (BP_hardware_subarch, boot_params, hdr.hardware_subarch);OFFSET (BP_version, boot_params, hdr.version);OFFSET (BP_kernel_alignment, boot_params, hdr.kernel_alignment); +OFFSET (BP_relocate_offset, boot_params, relocate_offset);BLANK ();DEFINE (PAGE_SIZE_asm,PAGE_SIZE );
arch/x86/kernel/cpu/perf_event.c +4 -0
@@ -26,8 +26,10 @@#include <asm/apic.h> #include <asm/stacktrace.h> #include <asm/nmi.h> +#include <asm/setup.h> static u64 perf_event_mask__read_mostly ; +static s32 relocate_offset;/* The maximal number of PEBS events: */ #define MAX_PEBS_EVENTS 4
@@ -2173,6 +2175,8 @@ void __init init_hw_perf_events(void)pr_info ("Performance Events: " ); + relocate_offset = boot_params.relocate_offset; +switch (boot_cpu_data.x86_vendor) {case X86_VENDOR_INTEL : err =intel_pmu_init ();
Signature · 1 line
1.6.1.2
Re: [PATCH 1/3] x86: record relocation offset
Em Wed, Dec 30, 2009 at 11:16:57AM +0800, Xiao Guangrong escreveu:
Quoted 10 lines
Record relocation offset, perf tools will use it
to adjust kernel symbol addressSigned-off-by Xiao Guangrong <[email protected]>arch/x86/boot/compressed/head_32.S | 2 ++ arch/x86/boot/compressed/head_64.S | 3 +++ arch/x86/include/asm/bootparam.h | 3 ++- arch/x86/kernel/asm-offsets_32.c | 1 + arch/x86/kernel/asm-offsets_64.c | 1 + arch/x86/kernel/cpu/perf_event.c | 4 ++++
<SNIP>
Quoted 10 lines
arch/x86/kernel/cpu/perf_event.c +2
-0@@ -26,8 +26,10 @@#include <asm/nmi.h> +#include <asm/setup.h> static u64 perf_event_mask__read_mostly ; +static s32 relocate_offset;
arch/x86/kernel/cpu/perf_event.c void __init init_hw_perf_events(void) · line 2179
Quoted 5 lines
arch/x86/kernel/cpu/perf_event.c +1
-0@@ -2173,6 +2175,8 @@ void __init init_hw_perf_events(void)pr_info ("Performance Events: " ); + relocate_offset = boot_params.relocate_offset;switch (boot_cpu_data.x86_vendor) {case X86_VENDOR_INTEL :
I'm no expert on the intricacies of boot_params, but all the other hunks seems sensible, but can't we provide a non-perf specific way of getting the relocate_offset? I guess other tools would also love to have it.
What about systemtap, don't they solve this in some other way? Frank?
- Arnaldo
H. Peter Anvin
reviewerRe: [PATCH 1/3] x86: record relocation offset
Quoted 7 lines · Arnaldo Carvalho de Melo
I'm no expert on the intricacies of
boot_params, but all the other hunks seems sensible, but can't we provide a non-perf specific way of getting therelocate_offset? I guess other tools would also love to have it.What about systemtap, don't they solve this in some other way? Frank?
I at one point proposed that boot_params should be exported in toto via sysfs. This got rather brutally shut down as "it's just a debugging feature" and got moved to debugfs (/debug/boot_params/data). However, the entire boot_params structure is available there.
Regardless of the reporting method, the patch passing this in by modifying the early assembly code, though, is more than a little pointless. The kernel already knows where it is loaded -- obviously, by sheer necessity -- and knows how it was itself configured, and as such we can do this calculation in C code without modifying boot_params or the early bootstrap.
-hpa
Signature · 2 lines
H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
Re: [PATCH 1/3] x86: record relocation offset
Em Wed, Dec 30, 2009 at 11:45:30AM -0800, H. Peter Anvin escreveu:
Quoted 12 lines · Arnaldo Carvalho de Melo
Quoted 5 lines
I'm no expert on the intricacies of
boot_params, but all the other hunks seems sensible, but can't we provide a non-perf specific way of getting therelocate_offset? I guess other tools would also love to have it.What about systemtap, don't they solve this in some other way? Frank?
I at one point proposed that
boot_paramsshould be exported in toto via sysfs. This got rather brutally shut down as "it's just a debugging feature" and got moved to debugfs (/debug/boot_params/data). However, the entireboot_paramsstructure is available there.
Quoted 6 lines
Regardless of the reporting method, the patch passing this in by modifying the early assembly code, though, is more than a little pointless. The kernel already knows where it is loaded -- obviously, by sheer necessity -- and knows how it was itself configured, and as such we can do this calculation in C code without modifying
boot_paramsor the early bootstrap.
Yeah, rereading the start of this discussion it now seems to me that what is happening is that a valid vmlinux is found, i.e. one with the same buildid as the buildid found in the perf.data file but then the kernel, at the time of perf record, was relocated, not matching what is in the vmlinux file.
So what we need to do is to figure this out at 'perf record' time and encode this in the header, so that later, at 'perf report' time, we can use a matching vmlinux and do the relocation (store this relocation offset in struct map->start for the kernel map) to get the right results.
Problem is that at 'perf record' time we may not have access to the vmlinux file, and thus not be able to figure out the relocation applied in that boot.
Then, at a later time, and possibly on another machine, on another arch, we try to map back IPs to symbols, the /proc/kallsyms is completely unrelated and we now have a vmlinux unrelocated...
So we need a way to get the relocation applied at 'perf record' time and encode it in the perf.data header. Ideas about how to do that?
- Arnaldo
Re: [PATCH 1/3] x86: record relocation offset
Em Wed, Dec 30, 2009 at 06:39:36PM -0200, Arnaldo Carvalho de Melo escreveu:
Quoted 10 lines
Em Wed, Dec 30, 2009 at 11:45:30AM -0800, H. Peter Anvin escreveu:
Quoted 4 lines
The kernel already knows where it is loaded -- obviously, by sheer necessity -- and knows how it was itself configured, and as such we can do this calculation in C code without modifying
boot_paramsor the early bootstrap.Problem is that at 'perf record' time we may not have access to the vmlinux file, and thus not be able to figure out the relocation applied in that boot.
Quoted 6 lines
Then, at a later time, and possibly on another machine, on another arch, we try to map back IPs to symbols, the
/proc/kallsymsis completely unrelated and we now have a vmlinux unrelocated...So we need a way to get the relocation applied at 'perf record' time and encode it in the perf.data header. Ideas about how to do that?
Well, I guess we could do the _stext trick again, storing its value, taken from /proc/kallsyms, into the perf.data header, then figuring out the relocation by looking at its value in the vmlinux symtab.
There were concerns in the past about relying on _stext, IIRC, James?
- Arnaldo
Re: [PATCH 1/3] x86: record relocation offset
Quoted 15 lines · Arnaldo Carvalho de Melo
Em Wed, Dec 30, 2009 at 06:39:36PM -0200, Arnaldo Carvalho de Melo escreveu:
Quoted 14 lines
Em Wed, Dec 30, 2009 at 11:45:30AM -0800, H. Peter Anvin escreveu:
Quoted 4 lines
The kernel already knows where it is loaded -- obviously, by sheer necessity -- and knows how it was itself configured, and as such we can do this calculation in C code without modifying
boot_paramsor the early bootstrap.Problem is that at 'perf record' time we may not have access to the vmlinux file, and thus not be able to figure out the relocation applied in that boot.
Then, at a later time, and possibly on another machine, on another arch, we try to map back IPs to symbols, the
/proc/kallsymsis completely unrelated and we now have a vmlinux unrelocated...
Quoted 6 lines
Quoted 2 lines
So we need a way to get the relocation applied at 'perf record' time and encode it in the perf.data header. Ideas about how to do that?
Well, I guess we could do the
_stexttrick again, storing its value, taken from/proc/kallsyms, into the perf.data header, then figuring out the relocation by looking at its value in the vmlinux symtab.
So reading the thread, I think the problem only exists for x86 compiled as a relocateable kernel.
Quoted 1 line
There were concerns in the past about relying on
_stext, IIRC, James?
Well, the original concerns were that _text relative relocation resolution only works for the core kernel, not for modules. Additionally, the kernel is in several sections, most notably init and runtime ... these may get loaded at different locations so _text relative symbol resolution won't work in init sections.
Right at the moment, only x86 and ppc do a relocatable kernel, and, as I understand the process, the whole kernel image gets a relative offset applied, so all sections get the same offset. Thus, for this case it looks like computing the offset from any known symbol would work (including _text).
James
PATCH 2/3 perf_event: support getting relocation offset
In reply to Xiao GuangrongSupport getting relocation offset by using 'inject' event
--- arch/x86/kernel/cpu/perf_event.c | 6 ++++++ include/linux/perf_event.h | 1 + kernel/perf_event.c | 23 +++++++++++++++++++++-- 3 files changed, 28 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/perf_event.c +6 -0
@@ -2470,3 +2470,9 @@ void hw_perf_event_setup_online(int cpu) {init_debug_store_on_cpu (cpu); } + +int perf_inject_get_relocate_offset (u64 *offset) +{ + *offset = relocate_offset; +return 0 ; +}
include/linux/perf_event.h +1 -0
@@ -428,6 +428,7 @@ enum perf_event_type {enum perf_inject_event {PERF_INJECT_HZ =0x01 , +PERF_INJECT_RELOCATE_OFFSET =0x02 , };enum perf_callchain_context {
kernel/perf_event.c +21 -2
@@ -2012,6 +2012,12 @@ unlock:return ret; } +extern __weak int perf_inject_get_relocate_offset (u64 *offset) +{ + *offset =0 ; +return 0 ; +} +static int perf_inject_get_hz (u64 *hz) { *hz =HZ ;
@@ -2050,10 +2056,23 @@ exit:static int perf_inject_ioctl (struct perf_event *event,unsigned int arg) { -if (!arg || arg & ~PERF_INJECT_HZ ) +int ret =0 ; + +if (!arg || arg & ~(PERF_INJECT_HZ |PERF_INJECT_RELOCATE_OFFSET ))return -EINVAL ; -return perf_inject_event (event,PERF_INJECT_HZ , perf_inject_get_hz); +if (arg &PERF_INJECT_HZ ) { + ret =perf_inject_event (event,PERF_INJECT_HZ , + perf_inject_get_hz); +if (ret) + goto exit; + } + +if (arg &PERF_INJECT_RELOCATE_OFFSET ) + ret =perf_inject_event (event,PERF_INJECT_RELOCATE_OFFSET , + perf_inject_get_relocate_offset); +exit: +return ret; }static int perf_event_set_output (struct perf_event *event,int output_fd);
Signature · 1 line
1.6.1.2
PATCH 3/3 perf tools: adjust symbol address
In reply to Xiao GuangrongUsing relocation offset adjust symbol address if we get kernel symbol name form elf file
--- tools/perf/builtin-record.c | 3 +++ tools/perf/util/session.c | 6 ++++++ tools/perf/util/symbol.c | 13 +++++++++++++ tools/perf/util/symbol.h | 2 ++ 4 files changed, 24 insertions(+), 0 deletions(-)
tools/perf/builtin-record.c +3 -0
@@ -436,6 +436,9 @@ static int __cmd_record(int argc, const char **argv)signal (SIGCHLD , sig_handler);signal (SIGINT , sig_handler); +/* Always get relocation offset */ + inject_events |=PERF_INJECT_RELOCATE_OFFSET ; +if (forks && (pipe (child_ready_pipe) <0 ||pipe (go_pipe) <0 )) {perror ("failed to create pipes" );exit (-1 );
tools/perf/util/session.c +6 -0
@@ -243,6 +243,12 @@ static int perf_session__process_event(struct perf_session *self,case PERF_RECORD_UNTHROTTLE :return ops->unthrottle (event, self);case PERF_RECORD_INJECT : +if (event->inject.inject_event_id == +PERF_INJECT_RELOCATE_OFFSET ) { +update_relocate_offset ((s32 )event->inject.value); +return 0 ; + } +return ops->inject (event, self);default : self->unknown_events++;
tools/perf/util/symbol.c +13 -0
@@ -19,6 +19,18 @@#define NT_GNU_BUILD_ID 3#endif +static s32 relocate_offset; +void update_relocate_offset (s32 offset) +{ + relocate_offset = offset; +} + +static inline void update_kernel_address (GElf_Sym *sym,bool kernel) +{ +if (kernel) + sym->st_value += relocate_offset; +} +enum dso_origin {DSO__ORIG_KERNEL =0 ,DSO__ORIG_JAVA_JIT ,
@@ -1012,6 +1024,7 @@ static int dso__load_sym(struct dso *self, struct map *map,if (demangled !=NULL ) elf_name = demangled; new_symbol: +update_kernel_address (&sym, kernel); f =symbol__new (sym.st_value, sym.st_size, elf_name);free (demangled);if (!f)
tools/perf/util/symbol.h +2 -0
@@ -10,6 +10,8 @@#define DEBUG_CACHE_DIR ".debug" +void update_relocate_offset (s32 offset); +#ifdef HAVE_CPLUS_DEMANGLE extern char *cplus_demangle (const char *,int );
Signature · 1 line
1.6.1.2
Re: [PATCH 3/3] perf tools: adjust symbol address
Em Wed, Dec 30, 2009 at 11:18:55AM +0800, Xiao Guangrong escreveu:
Quoted 12 lines
Using relocation offset adjust symbol address if we get kernel symbol name form elf file
tools/perf/util/symbol.c +1
-0@@ -19,6 +19,18 @@#define NT_GNU_BUILD_ID 3#endif +static s32 relocate_offset;
tools/perf/util/symbol.c line 32
Quoted 10 lines
tools/perf/util/symbol.c +10
-0+void update_relocate_offset (s32 offset) +{ + relocate_offset = offset; +} + +static inline void update_kernel_address (GElf_Sym *sym,bool kernel) +{ +if (kernel) + sym->st_value += relocate_offset; +}
This should be done on the dso level, we may process multiple kernels, some with relocation, some without.
Humm, even at the _map_ level, because then we can just use the normal map_ip mechanism, this time the not using the identity map stuff, i.e. we have to get an IP from some event, then subtract the relocate_offset that will be in map->start.
- Arnaldo
Re: [PATCH 3/3] perf tools: adjust symbol address
Quoted 12 lines · Arnaldo Carvalho de Melo
Em Wed, Dec 30, 2009 at 11:18:55AM +0800, Xiao Guangrong escreveu:
Quoted 11 lines
Using relocation offset adjust symbol address if we get kernel symbol name form elf file
tools/perf/util/symbol.c +0
-0@@ -19,6 +19,18 @@#define NT_GNU_BUILD_ID 3#endif
Quoted 15 lines
tools/perf/util/symbol.c line 32
Quoted 11 lines
tools/perf/util/symbol.c +11
-0+static s32 relocate_offset; +void update_relocate_offset (s32 offset) +{ + relocate_offset = offset; +} + +static inline void update_kernel_address (GElf_Sym *sym,bool kernel) +{ +if (kernel) + sym->st_value += relocate_offset; +}This should be done on the dso level, we may process multiple kernels, some with relocation, some without.
Sorry, what does the 'multiple kernels' means?
vmlinux* not know it's relocation or not, and we just handle the _specific_ kernel at the time which match the current system.
And i think adjust symbol address on the dso level is not a good idea since we hardly know it's a module address or kernel address on dso level, i.e. hardly to know whether the address need adjust.
Quoted 5 lines
Humm, even at the _map_ level, because then we can just use the normal
map_ipmechanism, this time the not using the identity map stuff, i.e. we have to get an IP from some event, then subtract therelocate_offsetthat will be inmap->start.
The 'inject' event is the first event in perf.data since we inject it at the first counter file and inject 'relocation offset' before enable event, i.e. before getting symbol address we have got the 'relocation offset' already.
Thanks,
Xiao
Re: [PATCH 3/3] perf tools: adjust symbol address
Em Thu, Dec 31, 2009 at 10:59:35AM +0800, Xiao Guangrong escreveu:
Quoted 30 lines
Quoted 12 lines · Arnaldo Carvalho de Melo
Em Wed, Dec 30, 2009 at 11:18:55AM +0800, Xiao Guangrong escreveu:
Quoted 11 lines
Using relocation offset adjust symbol address if we get kernel symbol name form elf file
tools/perf/util/symbol.c +0
-0@@ -19,6 +19,18 @@#define NT_GNU_BUILD_ID 3#endif Quoted 14 lines
tools/perf/util/symbol.c line 32
Quoted 11 lines
tools/perf/util/symbol.c +11
-0+static s32 relocate_offset; +void update_relocate_offset (s32 offset) +{ + relocate_offset = offset; +} + +static inline void update_kernel_address (GElf_Sym *sym,bool kernel) +{ +if (kernel) + sym->st_value += relocate_offset; +}This should be done on the dso level, we may process multiple kernels, some with relocation, some without.
Quoted 1 line
Sorry, what does the 'multiple kernels' means?
perf diff? I think you are combining the 'perf record' and 'perf report' steps as a single action...
Quoted 2 lines
vmlinux* not know it's relocation or not, and we just handle the _specific_ kernel at the time which match the current system.
'perf record' in one machine + 'perf report' in another should be possible.
Quoted 3 lines
And i think adjust symbol address on the dso level is not a good idea since we hardly know it's a module address or kernel address on dso level, i.e. hardly to know whether the address need adjust.
yeah, as I contininued below, its not the right level, for other reasons.
Quoted 9 lines
Quoted 5 lines
Humm, even at the _map_ level, because then we can just use the normal
map_ipmechanism, this time the not using the identity map stuff, i.e. we have to get an IP from some event, then subtract therelocate_offsetthat will be inmap->start.The 'inject' event is the first event in perf.data since we inject it at the first counter file and inject 'relocation offset' before enable event, i.e. before getting symbol address we have got the 'relocation offset' already.
There is no need for kernel changes, as the discussion showed.
- Arnaldo
Re: [PATCH 3/3] perf tools: adjust symbol address
Quoted 6 lines · Arnaldo Carvalho de Melo
Quoted 2 lines
vmlinux* not know it's relocation or not, and we just handle the _specific_ kernel at the time which match the current system.
'perf record' in one machine + 'perf report' in another should be possible.
Yeah, but current code not support this since it not record kernel build-id in perf.data while 'perf record' works, maybe you can fix it.
Xiao
Re: [PATCH 3/3] perf tools: adjust symbol address
Em Thu, Dec 31, 2009 at 06:49:01PM +0800, Xiao Guangrong escreveu:
Quoted 7 lines
Quoted 3 lines · Arnaldo Carvalho de Melo
Quoted 2 lines
vmlinux* not know it's relocation or not, and we just handle the _specific_ kernel at the time which match the current system.
Quoted 6 lines
Quoted 3 lines
'perf record' in one machine + 'perf report' in another should be possible.
Yeah, but current code not support this since it not record kernel build-id in perf.data while 'perf record' works, maybe you can fix it.
Huh? Checking...
[root@ana tmp]# perf record -a -f sleep 1s
[ perf record: Woken up 3 times to write data ]
[ perf record: Captured and wrote 0.330 MB perf.data (~14404 samples) ] [root@ana tmp]# perf buildid-list | grep kallsyms a3301c8755357466e39d71b46e8f69aecf83c0e8 [kernel.kallsyms] a3301c8755357466e39d71b46e8f69aecf83c0e8 [kernel.kallsyms] [root@ana tmp]#
In fact there is a bug, but the bug is either in 'perf buildid-list' showing it twice or it being recorded twice in 'perf record'.
- Arnaldo
Re: [PATCH 3/3] perf tools: adjust symbol address
Quoted 22 lines · Arnaldo Carvalho de Melo
Em Thu, Dec 31, 2009 at 06:49:01PM +0800, Xiao Guangrong escreveu:
Quoted 10 lines
Quoted 5 lines · Arnaldo Carvalho de Melo
Quoted 2 lines
vmlinux* not know it's relocation or not, and we just handle the _specific_ kernel at the time which match the current system.
'perf record' in one machine + 'perf report' in another should be possible.
Yeah, but current code not support this since it not record kernel build-id in perf.data while 'perf record' works, maybe you can fix it.
Huh? Checking...
[root@ana tmp]# perf record -a -f sleep 1s
[ perf record: Woken up 3 times to write data ]
[ perf record: Captured and wrote 0.330 MB perf.data (~14404 samples) ] [root@ana tmp]# perf buildid-list | grep kallsymsa3301c8755357466e39d71b46e8f69aecf83c0e8[kernel.kallsyms]a3301c8755357466e39d71b46e8f69aecf83c0e8[kernel.kallsyms] [root@ana tmp]#
Quoted 3 lines
In fact there is a bug, but the bug is either in 'perf buildid-list' showing it twice or it being recorded twice in 'perf record'.
Ah, it seems some perf tools like 'perf kmem/sched' not use the build-id which it's recorded in perf.data and it use the current kernel's build-id:
perf kmem/sched -> perf_session__new() -> perf_session__create_kernel_maps() -> map_groups__create_kernel_maps() -> dsos__create_kernel():
sysfs__read_build_id("/sys/kernel/notes", kernel->build_id,
sizeof(kernel->build_id)
Hope i not misunderstand it. :-)
Xiao