linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Dominik Brodowski <linux@brodo.de>
Cc: Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	albert@users.sourceforge.net
Subject: Re: ACPI PM-Timer [Was: Re: [RFC][PATCH] must fix lists]
Date: 27 Oct 2003 10:42:34 -0800	[thread overview]
Message-ID: <1067280154.1113.334.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <20031027182416.GA3905@brodo.de>

On Mon, 2003-10-27 at 10:24, Dominik Brodowski wrote:
> On Mon, Oct 27, 2003 at 11:53:43PM +1100, Nick Piggin wrote:
> > +o alan, Albert Cahalan: 1000 HZ timer increases the need for a stable time
> > +  source. Many laptops, SMI can lose ticks. ACPI timers? TSC?
> 
> A few months ago, I proposed to make the ACPI "Powermanagement" timer, a 
> reliable timing source with  ~3.6MHz resolution, available as a timer_opts
> for arch/i386/kernel/timers/timer.c. [1]
> 
> The major difficulty with this ACPI PM-Timer is that the I/O-port it is
> located at is unknown during time_init.[2] So, it becomes necessary to use a
> different timing source in the beginning, and switch to the ACPI PM-Timer
> later.
> 
> Here are two different methods to replace one timing source with another.
> First, the simple (and buggy) one -- the timing is broken until the next
> timer "tick" == the next call to mark_offset().

Thanks for working on this, Dominik!  

My only comment is that rather then replacing the time source midstream,
could we not do as the HPET time source does and use the late_time_init
callback? That avoids the nasty time source switching code. 

thanks
-john


  reply	other threads:[~2003-10-27 18:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  5:46 [RFC] must fix lists Nick Piggin
2003-10-21  9:36 ` Lars Marowsky-Bree
2003-10-22  0:40   ` Nick Piggin
2003-10-21 16:18 ` Randy.Dunlap
2003-10-22  2:50 ` Albert Cahalan
2003-10-23 21:11   ` Alan Cox
2003-10-23 21:09 ` Alan Cox
2003-10-23 23:46   ` Nick Piggin
2003-10-24  1:06     ` Albert Cahalan
2003-10-24  1:55     ` viro
2003-10-24  0:23   ` Chris Wright
2003-10-25 20:18     ` Alan Cox
2003-10-27 12:53       ` [RFC][PATCH] " Nick Piggin
2003-10-27 18:24         ` ACPI PM-Timer [Was: Re: [RFC][PATCH] must fix lists] Dominik Brodowski
2003-10-27 18:42           ` john stultz [this message]
2003-10-27 18:49             ` Dominik Brodowski
2003-10-27 19:07               ` john stultz
2003-10-27 23:01                 ` ACPI PM-Timer rev.2 [Was: Re: ACPI PM-Timer [Was: Re: [RFC][PATCH] must fix lists]] Dominik Brodowski
2003-11-04 22:03                   ` john stultz

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=1067280154.1113.334.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).