diff options
| author | Xin Li (Intel) <[email protected]> | 2024-08-22 00:39:04 -0700 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2024-08-25 19:23:00 +0200 |
| commit | 0dfac6f267fa091aa348c6a6742b463c9e7c98e3 (patch) | |
| tree | 753793a5adee543d9c67738db958347c71392cf1 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 723edbd2ca5fb4c78ac4a5644511c63895fd1c57 (diff) | |
x86/entry: Test ti_work for zero before processing individual bits
In most cases, ti_work values passed to arch_exit_to_user_mode_prepare()
are zeros, e.g., 99% in kernel build tests. So an obvious optimization is
to test ti_work for zero before processing individual bits in it.
Omit the optimization when FPU debugging is enabled, otherwise the
FPU consistency check is never executed.
Intel 0day tests did not find a perfermance regression with this change.
Suggested-by: H. Peter Anvin (Intel) <[email protected]>
Signed-off-by: Xin Li (Intel) <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Link: https://lore.kernel.org/all/[email protected]
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions