openkylin
/
linux
mirror of https://gitee.com/openkylin/linux.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

posix-timer: Update comment 

Pick the cleanup to the comment in posix-timers.c from Richards all in
one conversion patch.

Originally-from: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <johnstul@us.ibm.com>
LKML-Reference: <20110201134419.487708516@linutronix.de>
This commit is contained in:
Richard Cochran 2011-02-01 13:52:15 +00:00 committed by Thomas Gleixner
parent bc2c8ea483
commit 0061748dd2
1 changed files with 7 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
kernel/posix-timers.c
View File

@ -102,11 +102,7 @@ static DEFINE_SPINLOCK(idr_lock);
/* /*
* CLOCKs: The POSIX standard calls for a couple of clocks and allows us * CLOCKs: The POSIX standard calls for a couple of clocks and allows us
* to implement others. This structure defines the various * to implement others. This structure defines the various
* clocks and allows the possibility of adding others. We * clocks.
* 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.
* *
* RESOLUTION: Clock resolution is used to round up timer and interval * RESOLUTION: Clock resolution is used to round up timer and interval
* times, NOT to report clock times, which are reported with as * 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 * necessary code is written. The standard says we should say
* something about this issue in the documentation... * something about this issue in the documentation...
* *
* FUNCTIONS: The CLOCKs structure defines possible functions to handle * FUNCTIONS: The CLOCKs structure defines possible functions to
* various clock functions. For clocks that use the standard * handle various clock functions.
* 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.
* *
* At this time all functions EXCEPT clock_nanosleep can be * The standard POSIX timer management code assumes the
* redirected by the CLOCKS structure. Clock_nanosleep is in * following: 1.) The k_itimer struct (sched.h) is used for
* there, but the code ignores it. * 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 * Permissions: It is assumed that the clock_settime() function defined
* for each clock will take care of permission checks. Some * for each clock will take care of permission checks. Some