From: Tony Lindgren <tony@atomide.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick for x86 version 050602-1
Date: Wed, 8 Jun 2005 18:40:33 -0700 [thread overview]
Message-ID: <20050609014033.GA30827@atomide.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6004EBD10C@scsmsx403.amr.corp.intel.com>
* Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com> [050608 15:14]:
>
> >-----Original Message-----
> >From: linux-kernel-owner@vger.kernel.org
> >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of
> >Jonathan Corbet
> >Sent: Tuesday, June 07, 2005 1:36 PM
> >To: Tony Lindgren
> >Cc: linux-kernel@vger.kernel.org
> >Subject: Re: [PATCH] Dynamic tick for x86 version 050602-1
> >
> >Tony Lindgren <tony@atomide.com> wrote:
> >
> >> --- linux-dev.orig/arch/i386/kernel/irq.c 2005-06-01
> >17:51:36.000000000 -0700
> >> +++ linux-dev/arch/i386/kernel/irq.c 2005-06-01
> >17:54:32.000000000 -0700
> >> [...]
> >> @@ -102,6 +103,12 @@ fastcall unsigned int do_IRQ(struct pt_r
> >> );
> >> } else
> >> #endif
> >> +
> >> +#ifdef CONFIG_NO_IDLE_HZ
> >> + if (dyn_tick->state & (DYN_TICK_ENABLED |
> >DYN_TICK_SKIPPING) && irq != 0)
> >> + dyn_tick->interrupt(irq, NULL, regs);
> >> +#endif
> >> +
> >> __do_IRQ(irq, regs);
> >
> >Forgive me if I'm being obtuse (again...), but this hunk doesn't look
> >like it would work well in the 4K stacks case. When 4K stacks
> >are being
> >used, dyn_tick->interrupt() will only get called in the nested
> >interrupt
> >case, when the interrupt stack is already in use. This change also
> >pushes the non-assembly __do_IRQ() call out of the else branch, meaning
> >that, when the switch is made to the interrupt stack (most of
> >the time),
> >__do_IRQ() will be called twice for the same interrupt.
> >
> >It looks to me like you want to put your #ifdef chunk *after* the call
> >to __do_IRQ(), unless you have some reason for needing it to happen
> >before the regular interrupt handler is invoked.
> >
>
> Good catch. This indeed looks like a bug.
> With 050602-1 version I am seeing double the number of calls to
> timer_interrupt routine than expected. Say, when all CPUs are fully
> busy,
> I see 2*HZ timer interrupt count in /proc/interrupts
>
> And things look normal once I change this hunk as below
>
> >> } else
> >> #endif
> >> +
> + {
> >> +#ifdef CONFIG_NO_IDLE_HZ
> >> + if (dyn_tick->state & (DYN_TICK_ENABLED |
> >DYN_TICK_SKIPPING) && irq != 0)
> >> + dyn_tick->interrupt(irq, NULL, regs);
> >> +#endif
> >> +
> >> __do_IRQ(irq, regs);
> + }
Cool. Sorry for not responding earlier, my hard drive crashed yesterday
morning... I also managed to fry my spare computer's motherboard
while trying to recover some data from the broken disk :)
I'll try to post an updated patch tomorrow.
Tony
next prev parent reply other threads:[~2005-06-09 1:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 22:14 [PATCH] Dynamic tick for x86 version 050602-1 Pallipadi, Venkatesh
2005-06-09 1:40 ` Tony Lindgren [this message]
2005-06-10 4:30 ` [PATCH] Dynamic tick for x86 version 050609-2 Tony Lindgren
2005-06-10 9:10 ` Pavel Machek
2005-06-10 15:10 ` Tony Lindgren
2005-06-13 4:54 ` Valdis.Kletnieks
2005-06-13 15:25 ` Tony Lindgren
2005-06-13 16:47 ` Valdis.Kletnieks
2005-06-13 18:01 ` Thomas Renninger
2005-06-13 18:22 ` Tony Lindgren
2005-06-13 19:07 ` Valdis.Kletnieks
2005-06-14 9:39 ` Thomas Renninger
2005-06-14 15:40 ` Valdis.Kletnieks
2005-06-13 17:09 ` Srivatsa Vaddagiri
2005-06-13 17:55 ` Andi Kleen
2005-06-13 18:37 ` Tony Lindgren
2005-06-13 18:51 ` Andi Kleen
2005-06-13 19:35 ` Tony Lindgren
2005-06-13 19:48 ` Valdis.Kletnieks
2005-06-13 18:27 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 1:36 [PATCH] Dynamic tick for x86 version 050602-1 Tony Lindgren
2005-06-02 1:54 ` Zwane Mwaikambo
2005-06-02 2:09 ` Tony Lindgren
2005-06-02 8:30 ` Christian Hesse
2005-06-07 20:36 ` Jonathan Corbet
2005-06-10 4:18 ` Tony Lindgren
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=20050609014033.GA30827@atomide.com \
--to=tony@atomide.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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