Martin Schwidefsky 8c071b0f19 s390/time: correct use of store clock fast ... The result of the store-clock-fast (STCKF) instruction is a bit fuzzy. It can happen that the value stored on one CPU is smaller than the value stored on another CPU, although the order of the stores is the other way around. This can cause deltas of get_tod_clock() values to become negative when they should not be. We need to be more careful with store-clock-fast, this patch partially reverts git commit e4b7b4238e666682555461fa52eecd74652f36bb "time: always use stckf instead of stck if available". The get_tod_clock() function now uses the store-clock-extended (STCKE) instruction. get_tod_clock_fast() can be used if the fuzziness of store-clock-fast is acceptable e.g. for wait loops local to a CPU. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>		2013-10-22 09:16:40 +02:00
..
asm	s390/time: correct use of store clock fast	2013-10-22 09:16:40 +02:00
uapi/asm	s390/ptrace: PTRACE_TE_ABORT_RAND	2013-07-16 12:21:56 +02:00