| Al Viro | e70f1d5 | 2016-12-26 00:48:37 -0500 | [diff] [blame] | 1 | #ifndef __S390_EXTABLE_H |
| 2 | #define __S390_EXTABLE_H |
| 3 | /* |
| 4 | * The exception table consists of pairs of addresses: the first is the |
| 5 | * address of an instruction that is allowed to fault, and the second is |
| 6 | * the address at which the program should continue. No registers are |
| 7 | * modified, so it is entirely up to the continuation code to figure out |
| 8 | * what to do. |
| 9 | * |
| 10 | * All the routines below use bits of fixup code that are out of line |
| 11 | * with the main instruction path. This means when everything is well, |
| 12 | * we don't even have to jump over them. Further, they do not intrude |
| 13 | * on our cache or tlb entries. |
| 14 | */ |
| 15 | |
| 16 | struct exception_table_entry |
| 17 | { |
| 18 | int insn, fixup; |
| 19 | }; |
| 20 | |
| 21 | static inline unsigned long extable_fixup(const struct exception_table_entry *x) |
| 22 | { |
| 23 | return (unsigned long)&x->fixup + x->fixup; |
| 24 | } |
| 25 | |
| 26 | #define ARCH_HAS_RELATIVE_EXTABLE |
| 27 | |
| 28 | #endif |