From: Dinakar Guniguntala <dino@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: John Hawkes <hawkes@jackhammer.engr.sgi.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
pj@sgi.com, nickpiggin@yahoo.com.au, akpm@osdl.org
Subject: Re: [PATCH] ia64 cpuset + build_sched_domains() mangles structures
Date: Tue, 23 Aug 2005 01:46:26 +0530 [thread overview]
Message-ID: <20050822201626.GC7686@in.ibm.com> (raw)
In-Reply-To: <20050822160719.GB6652@elte.hu>
On Mon, Aug 22, 2005 at 06:07:19PM +0200, Ingo Molnar wrote:
> great! Andrew, i'd suggest we try the merged patch attached below in
> -mm.
>
Ingo, unfortunately I am hitting panic's on stress testing. The panic
screen is attached in the .png below.
On debugging I found that the panic happens consistently in this line
of code in function find_busiest_group
*imbalance = min((max_load - avg_load) * busiest->cpu_power,
(avg_load - this_load) * this->cpu_power)
/ SCHED_LOAD_SCALE;
Here I find that the "this" pointer is still NULL. I verified this by
a quick hack as below in the same function and with this hack it seems
to run for hours
- if (!busiest || this_load >= max_load)
+ if (!this || !busiest || this_load >= max_load)
This can only happen if the none of the sched groups pointed to by the
'sd' of the current cpu contain the current cpu. I was wondering if
this had anything to do with the way that we are using RCU to assign/
read the 'sd' pointer.
Any thoughts ??
-Dinakar
next prev parent reply other threads:[~2005-08-22 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 14:50 [PATCH] ia64 cpuset + build_sched_domains() mangles structures John Hawkes
2005-08-22 7:08 ` Ingo Molnar
2005-08-22 14:14 ` Dinakar Guniguntala
2005-08-22 16:07 ` Ingo Molnar
2005-08-22 20:16 ` Dinakar Guniguntala [this message]
2005-08-22 20:18 ` Dinakar Guniguntala
2005-09-02 14:47 ` Dinakar Guniguntala
2005-08-22 20:38 ` Paul Jackson
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=20050822201626.GC7686@in.ibm.com \
--to=dino@in.ibm.com \
--cc=akpm@osdl.org \
--cc=hawkes@jackhammer.engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.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