diff options
| author | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2017-05-02 14:36:00 +0300 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2017-05-03 10:08:57 +0300 |
| commit | 07a63cbe8bcb6ba72fb989dcab1ec55ec6c36c7e (patch) | |
| tree | e7ef1fae73975159ed7886988db715af73e73d49 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 89c9fea3c8034cdb2fd745f551cde0b507fd6893 (diff) | |
| download | linux-07a63cbe8bcb6ba72fb989dcab1ec55ec6c36c7e.tar.xz | |
s390/cputime: fix incorrect system time
git commit c5328901aa1db134 "[S390] entry[64].S improvements" removed
the update of the exit_timer lowcore field from the critical section
cleanup of the .Lsysc_restore/.Lsysc_done and .Lio_restore/.Lio_done
blocks. If the PSW is updated by the critical section cleanup to point to
user space again, the interrupt entry code will do a vtime calculation
after the cleanup completed with an exit_timer value which has *not* been
updated. Due to this incorrect system time deltas are calculated.
If an interrupt occured with an old PSW between .Lsysc_restore/.Lsysc_done
or .Lio_restore/.Lio_done update __LC_EXIT_TIMER with the system entry
time of the interrupt.
Cc: stable@vger.kernel.org # 3.3+
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions