diff options
| author | Ingo Molnar <[email protected]> | 2015-04-30 07:12:46 +0200 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2015-05-19 15:48:05 +0200 |
| commit | fbce7782467553d09cfde39473d23bde4ad78270 (patch) | |
| tree | 80010c081a5ebf198ebdf0bf2bd8bceb93b03e8f /tools/perf/scripts/python | |
| parent | 82c0e45eb5c839a8cee3d8d8a82d0592c4f42773 (diff) | |
x86/fpu: Merge fpu__reset() and fpu__clear()
With recent cleanups and fixes the fpu__reset() and fpu__clear()
functions have become almost identical in functionality: the only
difference is that fpu__reset() assumed that the fpstate
was already active in the eagerfpu case, while fpu__clear()
activated it if it was inactive.
This distinction almost never matters, the only case where such
fpstate activation happens if if the init thread (PID 1) gets exec()-ed
for the first time.
So keep fpu__clear() and change all fpu__reset() uses to
fpu__clear() to simpify the logic.
( In a later patch we'll further simplify fpu__clear() by making
sure that all contexts it is called on are already active. )
Cc: Andy Lutomirski <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Dave Hansen <[email protected]>
Cc: Fenghua Yu <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Oleg Nesterov <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions