posix-timer: Update comment (0061748d) · Commits · e / devices / android_kernel_fairphone_FP5

kernel/posix-timers.c

+7 −18

Original line number	Diff line number	Diff line
		@@ -102,11 +102,7 @@ static DEFINE_SPINLOCK(idr_lock);
		/*
		* CLOCKs: The POSIX standard calls for a couple of clocks and allows us
		* to implement others. This structure defines the various
		* clocks and allows the possibility of adding others. We
		* provide an interface to add clocks to the table and expect
		* the "arch" code to add at least one clock that is high
		* resolution. Here we define the standard CLOCK_REALTIME as a
		* 1/HZ resolution clock.
		* clocks.
		*
		* RESOLUTION: Clock resolution is used to round up timer and interval
		* times, NOT to report clock times, which are reported with as
		@@ -116,20 +112,13 @@ static DEFINE_SPINLOCK(idr_lock);
		* necessary code is written. The standard says we should say
		* something about this issue in the documentation...
		*
		* FUNCTIONS: The CLOCKs structure defines possible functions to handle
		* various clock functions. For clocks that use the standard
		* system timer code these entries should be NULL. This will
		* allow dispatch without the overhead of indirect function
		* calls. CLOCKS that depend on other sources (e.g. WWV or GPS)
		* must supply functions here, even if the function just returns
		* ENOSYS. The standard POSIX timer management code assumes the
		* following: 1.) The k_itimer struct (sched.h) is used for the
		* timer. 2.) The list, it_lock, it_clock, it_id and it_pid
		* fields are not modified by timer code.
		* FUNCTIONS: The CLOCKs structure defines possible functions to
		* handle various clock functions.
		*
		* At this time all functions EXCEPT clock_nanosleep can be
		* redirected by the CLOCKS structure. Clock_nanosleep is in
		* there, but the code ignores it.
		* The standard POSIX timer management code assumes the
		* following: 1.) The k_itimer struct (sched.h) is used for
		* the timer. 2.) The list, it_lock, it_clock, it_id and
		* it_pid fields are not modified by timer code.
		*
		* Permissions: It is assumed that the clock_settime() function defined
		* for each clock will take care of permission checks. Some