From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: Rescheduling interrupts
Date: Tue, 22 Jan 2008 17:55:55 +0200 [thread overview]
Message-ID: <200801221755.56470.caglar@pardus.org.tr> (raw)
In-Reply-To: <20080122152333.GB19590@elte.hu>
Hi;
22 Oca 2008 Sal tarihinde, Ingo Molnar şunları yazmıştı:
> * S.Çağlar Onur <caglar@pardus.org.tr> wrote:
> > I grabbed the logs two times to make sure to catch needed info. 1st [1]
> > one is generated while "Rescheduling interrupts" wakeups ~200 times and
> > 2nd one generated for ~350 wakeups.
> >
> > [1] http://cekirdek.pardus.org.tr/~caglar/dmesg.1st
> > [2] http://cekirdek.pardus.org.tr/~caglar/dmesg.2nd
>
> thanks, these seem to be mostly normal wakeups from standard tasks:
>
> IPI from task kdm_greet:2118 on CPU#0:
> IPI from task X:2079 on CPU#1:
> IPI from task kdm_greet:2118 on CPU#0:
> IPI from task hald-addon-inpu:2009 on CPU#1:
> IPI from task events/0:7 on CPU#1:
> IPI from task bash:2129 on CPU#0:
> IPI from task kdm_greet:2118 on CPU#0:
> IPI from task events/0:7 on CPU#1:
> IPI from task events/0:7 on CPU#1:
> IPI from task events/0:7 on CPU#1:
> IPI from task bash:3902 on CPU#1:
> IPI from task bash:3902 on CPU#1:
> IPI from task amarokapp:3423 on CPU#1:
> IPI from task amarokapp:3423 on CPU#1:
> IPI from task amarokapp:3423 on CPU#1:
> IPI from task X:2079 on CPU#0:
> IPI from task yakuake:3422 on CPU#0:
> IPI from task X:2079 on CPU#1:
> IPI from task amarokapp:3423 on CPU#1:
> IPI from task amarokapp:3423 on CPU#1:
>
> could you also add a similar IPI printouts (with the same panic_timeout
> logic) to arch/x86/kernel/smp_32.c's smp_reschedule_interrupt() function
> - while still keeping the other printouts too?
>
> Could you also enable PRINTK_TIME timestamps, so that we can see the
> timings? (And do a "dmesg -n 1" so that the printks happen fast and the
> timings are accurate.) I'd suggest to increase CONFIG_LOG_BUF_SHIFT to
> 20, so that your dmesg buffer is large enough. Plus try to capture 100
> events, ok?
>
> My theory is that for whatever reason we get "repeat" IPIs: multiple
> reschedule IPIs although the other CPU only initiated one.
Ok, please see http://cekirdek.pardus.org.tr/~caglar/dmesg.3rd :)
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
next prev parent reply other threads:[~2008-01-22 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 23:19 Rescheduling interrupts S.Çağlar Onur
2008-01-22 10:57 ` Ingo Molnar
2008-01-22 12:55 ` S.Çağlar Onur
2008-01-22 15:23 ` Ingo Molnar
2008-01-22 15:37 ` Ingo Molnar
2008-01-22 16:00 ` S.Çağlar Onur
2008-01-22 15:55 ` S.Çağlar Onur [this message]
2008-01-22 16:05 ` Ingo Molnar
2008-01-22 16:11 ` S.Çağlar Onur
2008-01-22 16:22 ` S.Çağlar Onur
2008-01-22 17:03 ` Matt Mackall
2008-01-22 19:27 ` Ingo Molnar
[not found] ` <p73fxwoncs4.fsf@crumb.suse.de>
2008-01-23 15:52 ` Matt Mackall
2008-05-13 18:03 ` Vegard Nossum
2008-05-13 19:04 ` Vegard Nossum
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=200801221755.56470.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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