linux-kernel - Re: [GIT PULL] adaptive spinning mutexes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090114122131.021e96b0.akpm@linux-foundation.org>
Date:	Wed, 14 Jan 2009 12:21:31 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	mingo@...e.hu, torvalds@...ux-foundation.org,
	paulmck@...ux.vnet.ibm.com, ghaskins@...ell.com, matthew@....cx,
	andi@...stfloor.org, chris.mason@...cle.com,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-btrfs@...r.kernel.org, tglx@...utronix.de, npiggin@...e.de,
	pmorreale@...ell.com, SDietrich@...ell.com,
	dmitry.adamushko@...il.com, hannes@...xchg.org
Subject: Re: [GIT PULL] adaptive spinning mutexes

On Wed, 14 Jan 2009 20:50:50 +0100
Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> On Wed, 2009-01-14 at 11:36 -0800, Andrew Morton wrote:
> 
> > Do people enable CONFIG_SCHED_DEBUG?
> 
> Well, I have it always enabled, but I've honestly no idea if that makes
> me weird.

It'd be weird if you're not weird.

> > CONFIG_DEBUG_MUTEXES=n, CONFIG_SCHED_DEBUG=y is getting to be a pretty
> > small subset?
> 
> Could be, do you fancy me doing a sysctl? shouldn't be hard.

The /sys/debug knob depends upon CONFIG_SCHED_DEBUG, I assume?

umm, yes, I do think that it would be prudent to make this control
unconditionally available.  Experience tells us that any regressions
which this change causes could take a long time to turn up - sometimes
years.  By which time the people who are reporting the regressions are
running packaged kernels, and if that packaged kernel didn't enable
CONFIG_SCHED_DEBUG, we're a bit screwed.

Did we end up deciding to remove the CONFIG_DEBUG_MUTEXES=n dependency?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/