summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2008-07-21 10:57:15 +0200
committerIngo Molnar <mingo@elte.hu>2008-07-21 11:03:32 +0200
commit33a37eb411d193851c334060780ab834ba534292 (patch)
tree15eff4d19335ec69ef2c222c800a0073cf10b924 /firmware
parente27772b48df91a954a74b1411b57d83b945a58c7 (diff)
downloadop-kernel-dev-33a37eb411d193851c334060780ab834ba534292.zip
op-kernel-dev-33a37eb411d193851c334060780ab834ba534292.tar.gz
KVM: fix exception entry / build bug, on 64-bit
-tip testing found this build bug: arch/x86/kvm/built-in.o:(.text.fixup+0x1): relocation truncated to fit: R_X86_64_32 against `.text' arch/x86/kvm/built-in.o:(.text.fixup+0xb): relocation truncated to fit: R_X86_64_32 against `.text' arch/x86/kvm/built-in.o:(.text.fixup+0x15): relocation truncated to fit: R_X86_64_32 against `.text' arch/x86/kvm/built-in.o:(.text.fixup+0x1f): relocation truncated to fit: R_X86_64_32 against `.text' arch/x86/kvm/built-in.o:(.text.fixup+0x29): relocation truncated to fit: R_X86_64_32 against `.text' Introduced by commit 4ecac3fd. The problem is that 'push' will default to 32-bit, which is not wide enough as a fixup address. (and which would crash on any real fixup event even if it was wide enough) Introduce KVM_EX_PUSH to get the proper address push width on 64-bit too. Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud