On 1/26/22 17:58, Sean Christopherson wrote:
On Tue, Jan 25, 2022, Pavel Skripkin wrote:
Hi kvm developers,
while building newest kernel (0280e3c58f92b2fe0e8fbbdf8d386449168de4a8) with
mostly random config I met following warnings:
LD .tmp_vmlinux.btf
ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
in section `.fixup'
BTF .btf.vmlinux.bin.o
LD .tmp_vmlinux.kallsyms1
ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
in section `.fixup'
KSYMS .tmp_vmlinux.kallsyms1.S
AS .tmp_vmlinux.kallsyms1.S
LD .tmp_vmlinux.kallsyms2
ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
in section `.fixup'
KSYMS .tmp_vmlinux.kallsyms2.S
AS .tmp_vmlinux.kallsyms2.S
LD vmlinux
ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
in section `.fixup'
Yep, xen.c has unnecessary usage of .fixup. I'll get a patch sent.
Peter Zijlstra has already posted "x86,kvm/xen: Remove superfluous
.fixup usage".
Paolo
