From: Tony Lindgren <tony@atomide.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: vatsa@in.ibm.com, tuukka.tikkanen@elektrobit.com, akpm@osdl.org,
johnstul@us.ibm.com, linux-kernel@vger.kernel.org, ak@muc.de,
george@mvista.com
Subject: Re: [ck] [PATCH] dynamic-tick patch modified for SMP
Date: Wed, 17 Aug 2005 00:53:21 -0700 [thread overview]
Message-ID: <20050817075320.GC16992@atomide.com> (raw)
In-Reply-To: <200508162323.33333.kernel@kolivas.org>
* Con Kolivas <kernel@kolivas.org> [050816 06:23]:
> On Tue, 16 Aug 2005 23:19, Srivatsa Vaddagiri wrote:
> > On Tue, Aug 16, 2005 at 02:30:51AM +1000, Con Kolivas wrote:
> > > Time definitely was lost the longer the machine was running.
> >
> > I think I found the reason for time drift. Basically cur_timer->mark_offset
> > doesnt expect to be called from non-timer interrupt handler. Hence it drops
> > one jiffy from the lost count. I fixed this in some "crude" fashion and
> > time has not drifted so far or is pretty much close to what it was in
> > pre-smp version. Will find a neat way to fix this and post a patch soon.
> >
> > > You mean disable it at runtime or not compile it in at all? Disabling it
> > > at runtime caused what I described to you as PIT mode (long stalls etc).
> >
> > I think I have recreated this on a machine here. Disabling
> > CONFIG_DYN_TICK_APIC at compile-time didnt seem to make any difference.
> > Will look at this problem next.
>
> Excellent.
>
> Mind you the APIC dyntick never really worked well on the pre-smp version on
> any hardware I tried it on so if you get both the APIC and PIT version
> working well you're doing great.
Sounds good! I only got the APIC stuff working properly on P3, but not on P4.
Tony
prev parent reply other threads:[~2005-08-17 7:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 20:19 [PATCH] dynamic-tick patch modified for SMP Srivatsa Vaddagiri
2005-08-13 1:35 ` [ck] " Con Kolivas
2005-08-13 6:51 ` Con Kolivas
2005-08-13 11:37 ` Srivatsa Vaddagiri
2005-08-13 14:53 ` Con Kolivas
2005-08-13 16:46 ` Srivatsa Vaddagiri
2005-08-14 0:18 ` Con Kolivas
2005-08-14 4:15 ` Kyle Moffett
2005-08-15 15:47 ` Srivatsa Vaddagiri
2005-08-15 16:39 ` john stultz
2005-08-16 2:11 ` Srivatsa Vaddagiri
2005-08-15 15:35 ` Srivatsa Vaddagiri
2005-08-15 16:30 ` Con Kolivas
2005-08-16 13:19 ` Srivatsa Vaddagiri
2005-08-16 13:23 ` Con Kolivas
2005-08-17 7:53 ` Tony Lindgren [this message]
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=20050817075320.GC16992@atomide.com \
--to=tony@atomide.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tuukka.tikkanen@elektrobit.com \
--cc=vatsa@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox