public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: george anzinger <george@mvista.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tsc-disable_B9
Date: 09 Aug 2002 13:58:01 -0700	[thread overview]
Message-ID: <1028926681.1118.64.camel@cog> (raw)
In-Reply-To: <3D540ED3.58F200F6@mvista.com>

On Fri, 2002-08-09 at 11:49, george anzinger wrote:

> An interesting approach, however, could you take a look at
> the high-res-timers patch (see signature).  In that code (in

I skimmed the patch, and I like alot of the cleanups and tweaks you have
make to arch/i386/kernel/time.c. As the number of time sources are
growing with the TSC, PIT, and now the cyclone counter and ACPI timer
(also, doesn't MS have some sort of high res performance counter
standard they're pushing for in hardware?), I'm thinking of rearranging
and renaming some of the code to better allow these changes. The current
do_slow/fast_gettimeoffset plus in-function 'if(use_tsc)' switches are
getting to be messy with the new additions. 

However, this may be a 2.5 issue, so before I take my 2.4 fixes and port
them to a new infrastructure, I'd like it if someone chimed in and said
"do it" or "skip it" for 2.4.


> the TSC version), we use the TSC to update jiffies and
> _sub_jiffie (which is TSC counts into the next jiffie).  We
> also want to be able to "grab" a new TSC and figure the time
> quickly, without updating either jiffies or _sub_jiffie. 
> Your approach would, I think, mean that both jiffies and
> _sub_jiffie would be per cpu values, not impossible, but,
> well, hard.

I need to look over you code a bit more. It looks interesting though. 

 
> On the other hand, the high-res-timers patch also allows one
> to use the ACPI pm timer, and ignore TSC completely :)

Yea, having another source of time is always nice, as long as it works
reliably. After all this time related work I'm not sure if I'm going to
start wearing 3-4 watches or just screw it and wear none. :)

thank for the pointer and feedback.
-john

 


  reply	other threads:[~2002-08-09 21:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  1:53 [PATCH] tsc-disable_B9 john stultz
2002-08-08  2:15 ` [PATCH] cyclone-timer_A9 john stultz
2002-08-08 13:18   ` Alan Cox
2002-08-09  2:03     ` john stultz
2002-08-08 13:17 ` [PATCH] tsc-disable_B9 Alan Cox
2002-08-09  2:30   ` john stultz
2002-08-09  9:17     ` Alan Cox
2002-08-09 17:46       ` john stultz
2002-08-09 18:49         ` george anzinger
2002-08-09 20:58           ` john stultz [this message]
2002-08-13  1:23             ` James Cleverdon
2002-08-11 20:16         ` Alan Cox
2002-08-15 16:56     ` Andrea Arcangeli
2002-08-16 11:15       ` Alan Cox
2002-08-16 13:19         ` Mikael Pettersson
2002-08-21 13:12           ` Andrea Arcangeli
2002-08-21 14:10             ` Alan Cox
2002-08-21 14:33               ` Andrea Arcangeli
2002-08-21 15:01                 ` Alan Cox
2002-08-21 16:13                   ` Andrea Arcangeli
2002-08-21 16:25                     ` Alan Cox
2002-08-21 17:17                       ` Andrea Arcangeli
2002-08-21 17:34                         ` Alan Cox
2002-08-26 16:10                     ` Pavel Machek
2002-08-26 18:45                       ` Martin J. Bligh
2002-08-26 19:00                         ` Pavel Machek
2002-08-26 19:05                         ` Alan Cox
2002-08-26 20:19                           ` Martin J. Bligh
2002-08-26 19:18                         ` Richard B. Johnson
2002-08-26 19:42                           ` Pavel Machek
2002-08-26 20:23                           ` Alan Cox
2002-08-26 22:49                         ` Andrea Arcangeli

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=1028926681.1118.64.camel@cog \
    --to=johnstul@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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