summaryrefslogtreecommitdiffstats
path: root/block/blk-mq-tag.c
diff options
context:
space:
mode:
authorMartin Schwidefsky <schwidefsky@de.ibm.com>2013-11-22 12:04:18 +0100
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2013-11-25 09:15:41 +0100
commit8adbf78ec4839c1dc4ff20c9a1f332a7bc99e6e6 (patch)
tree303b6c395fd521916b999aa11f65738a68f68315 /block/blk-mq-tag.c
parent79c74ecbebf76732f91b82a62ce7fc8a88326962 (diff)
downloadop-kernel-dev-8adbf78ec4839c1dc4ff20c9a1f332a7bc99e6e6.zip
op-kernel-dev-8adbf78ec4839c1dc4ff20c9a1f332a7bc99e6e6.tar.gz
s390,time: revert direct ktime path for s390 clockevent device
Git commit 4f37a68cdaf6dea833cfdded2a3e0c47c0f006da "s390: Use direct ktime path for s390 clockevent device" makes use of the CLOCK_EVT_FEAT_KTIME clockevent option to avoid the delta calculation with ktime_get() in clockevents_program_event and the get_tod_clock() in s390_next_event. This is based on the assumption that the difference between the internal ktime and the hardware clock is reflected in the wall_to_monotonic delta. But this is not true, the ntp corrections are applied via changes to the tk->mult multiplier and this is not reflected in wall_to_monotonic. In theory this could be solved by using the raw monotonic clock but it is simpler to switch back to the standard clock delta calculation. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'block/blk-mq-tag.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud