diff options
author | Ingo Molnar <[email protected]> | 2015-06-08 08:33:56 +0200 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2015-06-08 08:47:46 +0200 |
commit | 4c8cd0c50d0b1559727bf0ec7ff27caeba2dfe09 (patch) | |
tree | bd477ba39b3ee39b9f6ecf64bfc74a602fa27d60 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 2cd23553b488589f287457b7396470f5e3c40698 (diff) |
x86/asm/entry: Untangle 'ia32_sysenter_target' into two entry points: entry_SYSENTER_32 and entry_SYSENTER_compat
So the SYSENTER instruction is pretty quirky and it has different behavior
depending on bitness and CPU maker.
Yet we create a false sense of coherency by naming it 'ia32_sysenter_target'
in both of the cases.
Split the name into its two uses:
ia32_sysenter_target (32) -> entry_SYSENTER_32
ia32_sysenter_target (64) -> entry_SYSENTER_compat
As per the generic naming scheme for x86 system call entry points:
entry_MNEMONIC_qualifier
where 'qualifier' is one of _32, _64 or _compat.
Cc: Andy Lutomirski <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Brian Gerst <[email protected]>
Cc: Denys Vlasenko <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions