From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: "Hidetoshi Seto" <seto.hidetoshi@jp.fujitsu.com>,
"Török Edwin" <edwintorok@gmail.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: scheduler bug: process running since 5124095h
Date: Tue, 30 Mar 2010 11:34:34 +0200 [thread overview]
Message-ID: <1269941674.5109.514.camel@twins> (raw)
In-Reply-To: <1269940324.19286.16.camel@marge.simson.net>
On Tue, 2010-03-30 at 11:12 +0200, Mike Galbraith wrote:
> On Tue, 2010-03-30 at 11:01 +0200, Peter Zijlstra wrote:
> > On Tue, 2010-03-30 at 15:22 +0900, Hidetoshi Seto wrote:
> > >
> > > [kernel/sched_debug.c]
> > > void proc_sched_set_task(struct task_struct *p)
> > > {
> > > :
> > > p->se.sum_exec_runtime = 0;
> > > p->se.prev_sum_exec_runtime = 0;
> > > p->nvcsw = 0;
> > > p->nivcsw = 0;
> > > }
> >
> > Urgh, that code should really die, bugger that latencytop relies on that
> > though. Arjan anything you can do to cure latencytop of this madness?
>
> I killed those 4 fields without _seeming_ to upset it.
OK, if Arjan doesn't complain I'll take it ;-)
prev parent reply other threads:[~2010-03-30 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BADD408.8080609@gmail.com>
2010-03-28 8:49 ` scheduler bug: process running since 5124095h Török Edwin
2010-03-29 10:52 ` Mike Galbraith
2010-03-29 10:54 ` Peter Zijlstra
2010-03-29 11:33 ` Mike Galbraith
2010-03-29 12:04 ` Hidetoshi Seto
2010-03-30 6:22 ` Hidetoshi Seto
2010-03-30 8:07 ` Mike Galbraith
2010-03-30 9:09 ` Mike Galbraith
2010-03-30 9:01 ` Peter Zijlstra
2010-03-30 9:12 ` Mike Galbraith
2010-03-30 9:34 ` Peter Zijlstra [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=1269941674.5109.514.camel@twins \
--to=peterz@infradead.org \
--cc=arjan@infradead.org \
--cc=edwintorok@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=seto.hidetoshi@jp.fujitsu.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 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.