diff options
| author | Anton Blanchard <anton@samba.org> | 2013-11-17 00:39:05 (GMT) |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-11-29 19:28:08 (GMT) |
| commit | 057a7c6968c341081754ef5fe7c4d33fbfbd5465 (patch) | |
| tree | 1c3ddc6ce7baf2d540a9cf773f82a7664c6a9e90 /kernel/latencytop.c | |
| parent | 80e6b610e7442644507d76a38a98e1ab68695ad6 (diff) | |
| download | linux-fsl-qoriq-057a7c6968c341081754ef5fe7c4d33fbfbd5465.tar.xz | |
powerpc/pseries: Duplicate dtl entries sometimes sent to userspace
commit 84b073868b9d9e754ae48b828337633d1b386482 upstream.
When reading from the dispatch trace log (dtl) userspace interface, I
sometimes see duplicate entries. One example:
# hexdump -C dtl.out
00000000 07 04 00 0c 00 00 48 44 00 00 00 00 00 00 00 00
00000010 00 0c a0 b4 16 83 6d 68 00 00 00 00 00 00 00 00
00000020 00 00 00 00 10 00 13 50 80 00 00 00 00 00 d0 32
00000030 07 04 00 0c 00 00 48 44 00 00 00 00 00 00 00 00
00000040 00 0c a0 b4 16 83 6d 68 00 00 00 00 00 00 00 00
00000050 00 00 00 00 10 00 13 50 80 00 00 00 00 00 d0 32
The problem is in scan_dispatch_log() where we call dtl_consumer()
but bail out before incrementing the index.
To fix this I moved dtl_consumer() after the timebase comparison.
Signed-off-by: Anton Blanchard <anton@samba.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions