diff options
| author | Arnd Bergmann <[email protected]> | 2017-11-02 12:42:00 +0100 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2017-11-02 08:27:21 -0600 |
| commit | 474f5da2354e9fd5376b968e4c5a0f1807dc19e8 (patch) | |
| tree | b044445f66d4541155eaada9c57f04650127d7bf /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | c091fbe9a26ee116d99e2c0ed010afb957a10365 (diff) | |
skd: use ktime_get_real_seconds()
Like many storage drivers, skd uses an unsigned 32-bit number for
interchanging the current time with the firmware. This will overflow in
y2106 and is otherwise safe.
However, the get_seconds() function is generally considered deprecated
since the behavior is different between 32-bit and 64-bit architectures,
and using it may indicate a bigger problem.
To annotate that we've thought about this, let's add a comment here
and migrate to the ktime_get_real_seconds() function that consistently
returns a 64-bit number.
Signed-off-by: Arnd Bergmann <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions