UML - Fix !NO_HZ busy-loop
PATCH 1/1 UML - Fix !NO_HZ busy-loop
[ This one needs to get into 2.6.24 ]
With NO_HZ disabled, the UML idle loop effectively becomes a busy loop, as it will sleep for no time.
The cause was forgetting to restart the tick after waking up from sleep. It was disabled before sleeping, and the remaining time used as the interval to sleep. So, the tick needs to be restarted when nanosleep finishes.
This is done by introducing after_sleep_interval, which is empty in the NO_HZ case, but which sets the tick starting in the !NO_HZ case.
--- arch/um/os-Linux/time.c | 54 +++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 51 insertions(+), 3 deletions(-)
arch/um/os-Linux/time.c +51 -3
@@ -59,7 +59,7 @@ long long disable_timer(void) {struct itimerval time = ((struct itimerval ) { {0 ,0 }, {0 ,0 } }); -if (setitimer (ITIMER_VIRTUAL , &time, &time) <0 ) +if (setitimer (ITIMER_VIRTUAL , &time, &time) <0 )printk (UM_KERN_ERR "disable_timer - setitimer failed, " "errno = %d\n" , errno);
@@ -74,13 +74,61 @@ long long os_nsecs(void)return timeval_to_ns (&tv); } +#ifdef UML_CONFIG_NO_HZ +static int after_sleep_interval (struct timespec *ts) +{ +} +#else +static inline long long timespec_to_us (const struct timespec *ts) +{ +return ((long long ) ts->tv_sec *UM_USEC_PER_SEC ) + + ts->tv_nsec /UM_NSEC_PER_USEC ; +} + +static int after_sleep_interval (struct timespec *ts) +{ +int usec =UM_USEC_PER_SEC /UM_HZ ; +long long start_usecs =timespec_to_us (ts); +struct timeval tv; +struct itimerval interval; + +/* +* It seems that rounding can increase the value returned from +* setitimer to larger than the one passed in. Over time, +* this will cause the remaining time to be greater than the +* tick interval. If this happens, then just reduce the first +* tick to the interval value. +*/ +if (start_usecs > usec) + start_usecs = usec; + tv = ((struct timeval ) { .tv_sec = start_usecs /UM_USEC_PER_SEC , + .tv_usec = start_usecs %UM_USEC_PER_SEC }); + interval = ((struct itimerval ) { {0 , usec }, tv }); + +if (setitimer (ITIMER_VIRTUAL , &interval,NULL ) ==-1 ) +return -errno; + +return 0 ; +} +#endif +extern void alarm_handler (int sig,struct sigcontext *sc);void idle_sleep (unsigned long long nsecs) { -struct timespec ts = { .tv_sec = nsecs /UM_NSEC_PER_SEC , - .tv_nsec = nsecs %UM_NSEC_PER_SEC }; +struct timespec ts; + +/* +* nsecs can come in as zero, in which case, this starts a +* busy loop. To prevent this, reset nsecs to the tick +* interval if it is zero. +*/ +if (nsecs ==0 ) + nsecs =UM_NSEC_PER_SEC /UM_HZ ; + ts = ((struct timespec ) { .tv_sec = nsecs /UM_NSEC_PER_SEC , + .tv_nsec = nsecs %UM_NSEC_PER_SEC });if (nanosleep (&ts, &ts) ==0 )alarm_handler (SIGVTALRM ,NULL ); +after_sleep_interval (&ts); }
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
Quoted 32 lines · On Tue, 27 Nov 2007 15:03:47 -0500 Jeff Dike <[email protected]> wrote:
[ This one needs to get into 2.6.24 ]
With
NO_HZdisabled, the UML idle loop effectively becomes a busy loop, as it will sleep for no time.The cause was forgetting to restart the tick after waking up from sleep. It was disabled before sleeping, and the remaining time used as the interval to sleep. So, the tick needs to be restarted when nanosleep finishes.
This is done by introducing
after_sleep_interval, which is empty in theNO_HZcase, but which sets the tick starting in the !NO_HZ case.Signed-off-by Jeff Dike <[email protected]>--- arch/um/os-Linux/time.c | 54 +++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 51 insertions(+), 3 deletions(-)Index:
linux-2.6.22/arch/um/os-Linux/time.c
===================================================================arch/um/os-Linux/time.c +1
-1@@ -59,7 +59,7 @@ long long disable_timer(void) {struct itimerval time = ((struct itimerval ) { {0 ,0 }, {0 ,0 } }); -if (setitimer (ITIMER_VIRTUAL , &time, &time) <0 ) +if (setitimer (ITIMER_VIRTUAL , &time, &time) <0 )printk (UM_KERN_ERR "disable_timer - setitimer failed, " "errno = %d\n" , errno);
arch/um/os-Linux/time.c long long os_nsecs(void) · line 77
Quoted 4 lines
arch/um/os-Linux/time.c +1
-0@@ -74,13 +74,61 @@ long long os_nsecs(void)return timeval_to_ns (&tv); } +#ifdef UML_CONFIG_NO_HZ
Nothing ever defines this?
Quoted 49 lines
arch/um/os-Linux/time.c +43
-2+static int after_sleep_interval (struct timespec *ts) +{ +} +#else +static inline long long timespec_to_us (const struct timespec *ts) +{ +return ((long long ) ts->tv_sec *UM_USEC_PER_SEC ) + + ts->tv_nsec /UM_NSEC_PER_USEC ; +} + +static int after_sleep_interval (struct timespec *ts) +{ +int usec =UM_USEC_PER_SEC /UM_HZ ; +long long start_usecs =timespec_to_us (ts); +struct timeval tv; +struct itimerval interval; + +/* +* It seems that rounding can increase the value returned from +* setitimer to larger than the one passed in. Over time, +* this will cause the remaining time to be greater than the +* tick interval. If this happens, then just reduce the first +* tick to the interval value. +*/ +if (start_usecs > usec) + start_usecs = usec; + tv = ((struct timeval ) { .tv_sec = start_usecs /UM_USEC_PER_SEC , + .tv_usec = start_usecs %UM_USEC_PER_SEC }); + interval = ((struct itimerval ) { {0 , usec }, tv }); + +if (setitimer (ITIMER_VIRTUAL , &interval,NULL ) ==-1 ) +return -errno; + +return 0 ; +} +#endif +extern void alarm_handler (int sig,struct sigcontext *sc);void idle_sleep (unsigned long long nsecs) { -struct timespec ts = { .tv_sec = nsecs /UM_NSEC_PER_SEC , - .tv_nsec = nsecs %UM_NSEC_PER_SEC }; +struct timespec ts; + +/* +* nsecs can come in as zero, in which case, this starts a +* busy loop. To prevent this, reset nsecs to the tick +* interval if it is zero.
arch/um/os-Linux/time.c long long os_nsecs(void) · line 134
Quoted 10 lines
arch/um/os-Linux/time.c +6
-0+*/ +if (nsecs ==0 ) + nsecs =UM_NSEC_PER_SEC /UM_HZ ; + ts = ((struct timespec ) { .tv_sec = nsecs /UM_NSEC_PER_SEC , + .tv_nsec = nsecs %UM_NSEC_PER_SEC });if (nanosleep (&ts, &ts) ==0 )alarm_handler (SIGVTALRM ,NULL ); +after_sleep_interval (&ts); }
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
Quoted 3 lines · Andrew Morton
Quoted 1 line
+#ifdef
UML_CONFIG_NO_HZNothing ever defines this?
$ grep HZ obj/arch/um/include/uml-config.h #define UML_CONFIG_NO_HZ 1
uml-config.h is auto-generated to provide the config definitions to the userspace side of UML.
Jeff
Signature · 11 lines
Work email - jdike at linux dot intel dot com ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ User-mode-linux-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel