ia64: enable CONFIG_DEBUG_SPINLOCK_SLEEP

On 20 Dec 2006 04:27:11 -0500
Jes Sorensen <jessgi.com> wrote:

> >>>>> "Andrew" == akpm 
<akpmosdl.org> writes:
> 
> Andrew> From: Andrew Morton <akpmosdl.org> Some trivial bugs are
> Andrew> coming from ia64 developers.  Try to help
them.
> 
> Ugh!
> 
> Please don't do this in the sn2 defconfig! Spin lock
debugging totally
> kills scalability. I'll end up with a ton of internal
complaints over
> the kernel not performing if this goes in :-(

Well you tell me how to stop ia64 developers from submitting
stuff which
has stupid bugs which instamanifest for everyone else?  It
is not uncommon.

-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

Andrew Morton wrote:
>> Please don't do this in the sn2 defconfig! Spin
lock debugging totally
>> kills scalability. I'll end up with a ton of
internal complaints over
>> the kernel not performing if this goes in :-(
> 
> Well you tell me how to stop ia64 developers from
submitting stuff which
> has stupid bugs which instamanifest for everyone else? 
It is not uncommon.

Beat them with a stick?

Seriously, not sure how to deal with it. I try and keep the
sn2_defconfig to match the actual hardware and my colleagues
rely on
being able to build that. With spin lock debugging enabled
we can barely
boot the system on medium to large boxes.

If you get stuff like that from someone with an sgi.com
address, let me
know and I'll apply the clue 2x4.

Cheers,
Jes
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

On Wed, 20 Dec 2006 10:46:40 +0100
Jes Sorensen <jessgi.com> wrote:

> Andrew Morton wrote:
> >> Please don't do this in the sn2 defconfig!
Spin lock debugging totally
> >> kills scalability. I'll end up with a ton of
internal complaints over
> >> the kernel not performing if this goes in :-(
> > 
> > Well you tell me how to stop ia64 developers from
submitting stuff which
> > has stupid bugs which instamanifest for everyone
else?  It is not uncommon.
> 
> Beat them with a stick?

Make it a pointy stick and I can improve on that.

I've been thinking that we could do with a CONFIG_RC_KERNEL
or something
which gets turned on up until -rc4 or so, then gets turned
off.  So we can
make the devel kernels more debugging-friendly.

The main problem would be remembering to turn the dang thing
off and on at
the right times.


-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

Andrew Morton wrote:
> Make it a pointy stick and I can improve on that.

Aye! aye! sir!

> I've been thinking that we could do with a
CONFIG_RC_KERNEL or something
> which gets turned on up until -rc4 or so, then gets
turned off.  So we can
> make the devel kernels more debugging-friendly.
> 
> The main problem would be remembering to turn the dang
thing off and on at
> the right times.

I like that idea! I wonder if we could somehow do this with
some script
magic? but we may also want to be able to offer it as a
config option
that people can force off if they want to (with some flashy
neon signs
telling them they are entering rogue territory).

Cheers,
Jes
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html