summaryrefslogtreecommitdiffstats
path: root/tools/perf/pmu-events/arch
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2021-06-24 11:41:22 +0200
committerPeter Zijlstra <peterz@infradead.org>2021-09-17 13:20:26 +0200
commit1462eb381b4c27576a3e818bc9f918765d327fdf (patch)
tree390e3dce4b9e3741f359316ae1d28d24bab555c9 /tools/perf/pmu-events/arch
parent847d9317b2b9c7ecc14b953e6ecf9c12bcdb42e9 (diff)
downloadlinux-1462eb381b4c27576a3e818bc9f918765d327fdf.tar.bz2
x86/xen: Rework the xen_{cpu,irq,mmu}_opsarrays
In order to allow objtool to make sense of all the various paravirt functions, it needs to either parse whole pv_ops[] tables, or observe individual assignments in the form: bf87: 48 c7 05 00 00 00 00 00 00 00 00 movq $0x0,0x0(%rip) bf92 <xen_init_spinlocks+0x5f> bf8a: R_X86_64_PC32 pv_ops+0x268 As is, xen_cpu_ops[] is at offset +0 in pv_ops[] and could thus be parsed as a 'normal' pv_ops[] table, however xen_irq_ops[] and xen_mmu_ops[] are not. Worse, both the latter two are compiled into the individual assignment for by current GCC, but that's not something one can rely on. Therefore, convert all three into full pv_ops[] tables. This has the benefit of not needing to teach objtool about the offsets and resulting in more conservative code-gen. Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Juergen Gross <jgross@suse.com> Link: https://lore.kernel.org/r/20210624095149.057262522@infradead.org
Diffstat (limited to 'tools/perf/pmu-events/arch')
0 files changed, 0 insertions, 0 deletions