All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Andrew Morton <akpm@osdl.org>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clean up FIXME in do_timer_interrupt
Date: Fri, 04 Mar 2005 02:28:39 -0800	[thread overview]
Message-ID: <42283857.9050007@mvista.com> (raw)
In-Reply-To: <1109899148.3630.5.camel@mindpipe>

Lee Revell wrote:
> On Thu, 2005-03-03 at 16:45 -0800, Andrew Morton wrote:
> 
>>If efi_enabled is true and efi_set_rtc_mmss(xtime.tv_sec) returns zero, the
>>new code will run set_rtc_mmss(xtime.tv_sec) whereas the old code won't.
> 
> 
> Argh, I should know better then to send patches before having coffee.
> 
> Here's a new patch.  Still ugly, but might be a worthwhile cleanup.

Lets ask the obvious question: Why isn't this update hung on a timer?  It seems 
silly to check this 6000 times per update.  I am sure we can sync a timer to the 
same degree we do timer interrupts, so there _must_ be some other reason.  Right?

George
> 
> Lee
> 
> --- linux-2.6.11-rc4-V0.7.39-02/arch/i386/kernel/time.c	2005-02-14 18:10:49.000000000 -0500
> +++ linux-2.6.11-rc4/arch/i386/kernel/time.c	2005-03-03 20:15:39.000000000 -0500
> @@ -254,16 +254,12 @@
>  			>= USEC_AFTER - ((unsigned) TICK_SIZE) / 2 &&
>  	    (xtime.tv_nsec / 1000)
>  			<= USEC_BEFORE + ((unsigned) TICK_SIZE) / 2) {
> -		/* horrible...FIXME */
> +	        last_rtc_update = xtime.tv_sec;
>  		if (efi_enabled) {
> -	 		if (efi_set_rtc_mmss(xtime.tv_sec) == 0)
> -				last_rtc_update = xtime.tv_sec;
> -			else
> -				last_rtc_update = xtime.tv_sec - 600;
> -		} else if (set_rtc_mmss(xtime.tv_sec) == 0)
> -			last_rtc_update = xtime.tv_sec;
> -		else
> -			last_rtc_update = xtime.tv_sec - 600; /* do it again in 60 s */
> +		    if (efi_set_rtc_mmss(xtime.tv_sec))
> +			last_rtc_update -= 600;
> +		} else if (set_rtc_mmss(xtime.tv_sec))
> +			last_rtc_update -= 600;
>  	}
>  
>  	if (MCA_bus) {
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/


  reply	other threads:[~2005-03-04 10:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 17:10 [PATCH] clean up FIXME in do_timer_interrupt Lee Revell
2005-03-04  0:45 ` Andrew Morton
2005-03-04  1:19   ` Lee Revell
2005-03-04 10:28     ` George Anzinger [this message]
2005-03-04 20:43       ` Lee Revell
2005-03-04 20:58         ` George Anzinger
2005-03-08 20:27           ` Lee Revell
2005-03-08 23:23             ` George Anzinger
2005-03-10  8:42               ` George Anzinger
2005-03-11 22:23                 ` Lee Revell
2005-03-11 22:34                   ` Andrew Morton
2005-03-12  2:01                     ` George Anzinger
2005-03-19  9:33                     ` [PATCH] clean up FIXME in do_timer_interrupt-lock fix George Anzinger
2005-03-19 21:21                       ` Andrew Morton
2005-03-19 22:23                         ` George Anzinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42283857.9050007@mvista.com \
    --to=george@mvista.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.