diff options
| author | Ani Sinha <[email protected]> | 2021-07-13 08:35:21 +0530 |
|---|---|---|
| committer | Wei Liu <[email protected]> | 2021-07-13 17:40:23 +0000 |
| commit | c445535c3efbfb8cb42d098e624d46ab149664b7 (patch) | |
| tree | 55dc142d1c0f20ceab0b84540b11bf9d3285eeb0 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | ba3f5839fbeb3f9e65070d90aa4e66008bbea80f (diff) | |
x86/hyperv: fix for unwanted manipulation of sched_clock when TSC marked unstable
Marking TSC as unstable has a side effect of marking sched_clock as
unstable when TSC is still being used as the sched_clock. This is not
desirable. Hyper-V ultimately uses a paravirtualized clock source that
provides a stable scheduler clock even on systems without TscInvariant
CPU capability. Hence, mark_tsc_unstable() call should be called _after_
scheduler clock has been changed to the paravirtualized clocksource. This
will prevent any unwanted manipulation of the sched_clock. Only TSC will
be correctly marked as unstable.
Signed-off-by: Ani Sinha <[email protected]>
Reviewed-by: Michael Kelley <[email protected]>
Tested-by: Michael Kelley <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Wei Liu <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions