public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schlichter <thomas.schlichter@web.de>
To: vatsa@in.ibm.com
Cc: john stultz <johnstul@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Updated dynamic tick patches - Fix lost tick
Date: Thu, 1 Sep 2005 09:42:23 +0200	[thread overview]
Message-ID: <200509010942.24026.thomas.schlichter@web.de> (raw)
In-Reply-To: <20050901072303.GB9760@in.ibm.com>

Am Donnerstag, 1. September 2005 09:23 schrieb Srivatsa Vaddagiri:
> On Thu, Sep 01, 2005 at 08:29:32AM +0200, Thomas Schlichter wrote:
> > I tested the attached patch during the last night and it sems to work...
>
> A quick feedback on your patch:
>
> A litmus test that I use is if "zero" lost ticks are being hit,
> which we should not w/o a patch like dynamic tick.
> 
> I still see zero lost ticks being reported with your patch (during
> bootup atleast) which means all is still not well?

I think this can happen due to this:
  http://bugzilla.kernel.org/show_bug.cgi?id=5127

Think about two adjacent regular timer interrupts. Now consider the first one 
is handled very late (indeed even after the second interrupt already 
occoured). Then will see two "lost" ticks.

Now directly the second timer interrupt handler is executed and, well it sees 
there has _nearly_ no time passed, so no "lost" ticks are reported.

I think this could explain it, right?!

Best regards
  Thomas Schlichter

  reply	other threads:[~2005-09-01  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  6:29 [PATCH 1/3] Updated dynamic tick patches - Fix lost tick Thomas Schlichter
2005-09-01  7:23 ` Srivatsa Vaddagiri
2005-09-01  7:42   ` Thomas Schlichter [this message]
2005-09-01 10:28     ` Srivatsa Vaddagiri
2005-09-01 11:05       ` Thomas Schlichter
2005-09-01 11:33         ` Srivatsa Vaddagiri

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=200509010942.24026.thomas.schlichter@web.de \
    --to=thomas.schlichter@web.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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