Searched hist:d1b1b600 (Results 1 – 4 of 4) sorted by relevance
| /freebsd/sys/kern/ |
| H A D | subr_dummy_vdso_tc.c | d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
|
| H A D | kern_tc.c | d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
|
| /freebsd/sys/sys/ |
| H A D | vdso.h | d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
|
| /freebsd/sys/x86/x86/ |
| H A D | tsc.c | d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
d1b1b600 Tue Jan 20 03:54:30 GMT 2015 Neel Natu <neel@FreeBSD.org> Update the vdso timehands only via tc_windup().
Prior to this change CLOCK_MONOTONIC could go backwards when the timecounter
hardware was changed via 'sysctl kern.timecounter.hardware'. This happened
because the vdso timehands update was missing the special treatment in
tc_windup() when changing timecounters.
Reviewed by: kib
|