From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Mike Galbraith <efault@gmx.de>
Cc: danial_thom@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: Measuring tools - top and interrupts
Date: Sat, 24 Jun 2006 21:25:23 +0200 [thread overview]
Message-ID: <20060624192523.GA3231@atjola.homenet> (raw)
In-Reply-To: <1151166193.8516.8.camel@Homer.TheSimpsons.net>
On 2006.06.24 18:23:12 +0200, Mike Galbraith wrote:
> On Sat, 2006-06-24 at 17:40 +0200, Björn Steinbrink wrote:
> > On 2006.06.24 13:41:57 +0200, Mike Galbraith wrote:
> > > On Sat, 2006-06-24 at 11:52 +0200, Mike Galbraith wrote:
> > > > On Sat, 2006-06-24 at 11:21 +0200, Björn Steinbrink wrote:
> > > > >
> > > > > The non-SMP call to update_process_times() is in do_timer_interrupt_hook(),
> > > > > so I guess the above is not the Right Thing to do.
> > > >
> > > > Ah, there it is. That's what I was looking for. I figured that doing
> > > > what I did had to be wrong, but tried it for grins anyway... was pretty
> > > > surprised when it worked (kinda).
> > >
> > > Calling update_process_times() in do_timer_interrupt_hook() flat does
> > > not work here. Calling it in smp_local_timer_interrupt() works fine.
> > >
> > > Oh joy.
> >
> > I can reproduce it now, seems to require CONFIG_4KSTACKS to fail. Can
> > you confirm that?
>
> What a coincidence. After trying a different compiler, and slogging
> through a bunch of assembler trying to figure out how the heck this can
> happen, I was just booting an 8k stack kernel (as a wild-ass guess;).
>
> let's see. Yeah, confirmed.
OK, it also depends on IO APIC being enabled and active, ie. noapic on
the kernel command line will fix it as well as disabling
CONFIG_X86_IO_APIC. That doesn't help me at all to understand why it
happens though.
The only difference with IO APIC disabled seems to be that the irq
doesn't get ACKed before update_process_times() gets called.
And your "fix" makes it being called outside of the xtime_lock spinlock
and with a slightly different stack usage AFAICT.
But none of these should make a difference, right?
Björn
next prev parent reply other threads:[~2006-06-24 19:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 15:26 Measuring tools - top and interrupts Danial Thom
2006-06-22 16:19 ` Randy.Dunlap
2006-06-22 17:16 ` Bernd Eckenfels
2006-06-22 16:21 ` Erik Mouw
2006-06-22 16:58 ` Danial Thom
2006-06-22 17:31 ` Erik Mouw
2006-06-22 23:37 ` Danial Thom
2006-06-23 8:32 ` Mike Galbraith
2006-06-23 20:14 ` Danial Thom
2006-06-23 22:51 ` Mike Galbraith
2006-06-23 9:02 ` Erik Mouw
2006-06-23 17:13 ` Alistair John Strachan
2006-06-23 18:16 ` Danial Thom
2006-06-23 5:34 ` sena seneviratne
2006-06-23 20:42 ` Danial Thom
2006-06-22 17:57 ` Francois Romieu
2006-06-22 22:47 ` Danial Thom
2006-06-22 23:53 ` Francois Romieu
2006-06-23 20:34 ` Danial Thom
2006-06-23 21:19 ` Francois Romieu
2006-06-24 2:07 ` Björn Steinbrink
2006-06-24 4:39 ` sena seneviratne
2006-06-24 5:59 ` Mike Galbraith
2006-06-24 6:26 ` Mike Galbraith
2006-06-24 9:21 ` Björn Steinbrink
2006-06-24 9:51 ` Mike Galbraith
2006-06-24 11:41 ` Mike Galbraith
2006-06-24 15:40 ` Björn Steinbrink
2006-06-24 16:23 ` Mike Galbraith
2006-06-24 19:25 ` Björn Steinbrink [this message]
2006-06-25 5:06 ` Mike Galbraith
2006-06-25 11:12 ` Björn Steinbrink
2006-06-25 14:24 ` [PATCH] i386: Fix softirq accounting with 4K stacks Björn Steinbrink
2006-06-25 15:15 ` Arjan van de Ven
2006-06-25 17:44 ` Mike Galbraith
2006-06-25 17:43 ` Arjan van de Ven
2006-06-25 18:42 ` Björn Steinbrink
2006-06-26 2:23 ` Mike Galbraith
2006-06-26 3:05 ` Mike Galbraith
2006-06-26 17:58 ` Björn Steinbrink
2006-06-27 10:09 ` Mike Galbraith
2006-06-25 20:45 ` Measuring tools - top and interrupts Danial Thom
2006-06-26 2:33 ` Mike Galbraith
2006-06-30 13:41 ` Danial Thom
2006-06-30 18:03 ` Mike Galbraith
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=20060624192523.GA3231@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=danial_thom@yahoo.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.