x86/kvm: Move kvm_fastop_exception to .fixup section
authorJosh Poimboeuf <jpoimboe@redhat.com>
Wed, 4 Oct 2017 15:39:05 +0000 (10:39 -0500)
committerRadim Krčmář <rkrcmar@redhat.com>
Thu, 5 Oct 2017 13:06:30 +0000 (15:06 +0200)
commitf26e60167d8b5b1c67b3efd4cb5672da446bdb0e
tree607ac1ada59e9a982c0e06ce6849a5da5a641142
parenta2b7861bb33b2538420bb5d8554153484d3f961f
x86/kvm: Move kvm_fastop_exception to .fixup section

When compiling the kernel with the '-frecord-gcc-switches' flag, objtool
complains:

  arch/x86/kvm/emulate.o: warning: objtool: .GCC.command.line+0x0: special: can't find new instruction

And also the kernel fails to link.

The problem is that the 'kvm_fastop_exception' code gets placed into the
throwaway '.GCC.command.line' section instead of '.text'.

Exception fixup code is conventionally placed in the '.fixup' section,
so put it there where it belongs.

Reported-and-tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
arch/x86/kvm/emulate.c