diff options
| author | Josh Poimboeuf <[email protected]> | 2017-10-04 15:39:05 +0000 |
|---|---|---|
| committer | Radim Krčmář <[email protected]> | 2017-10-05 13:06:30 +0000 |
| commit | f26e60167d8b5b1c67b3efd4cb5672da446bdb0e (patch) | |
| tree | 607ac1ada59e9a982c0e06ce6849a5da5a641142 /drivers/iio/trigger/stm32-timer-trigger.c | |
| parent | kvm/x86: Avoid async PF preempting the kernel incorrectly (diff) | |
| download | kernel-f26e60167d8b5b1c67b3efd4cb5672da446bdb0e.tar.gz kernel-f26e60167d8b5b1c67b3efd4cb5672da446bdb0e.zip | |
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 <[email protected]>
Signed-off-by: Josh Poimboeuf <[email protected]>
Reviewed-by: Paolo Bonzini <[email protected]>
Signed-off-by: Radim Krčmář <[email protected]>
Diffstat (limited to 'drivers/iio/trigger/stm32-timer-trigger.c')
0 files changed, 0 insertions, 0 deletions