[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B53B8DD.9000809@zytor.com>
Date: Sun, 17 Jan 2010 17:26:53 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
CC: Ozan Çağlayan <ozan@...dus.org.tr>,
Yinghai Lu <yinghai@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
mingo@...e.hu, a.p.zijlstra@...llo.nl, stable@...nel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jaswinder Singh Rajput <jaswinder@...nel.org>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: RFC: deprecate CONFIG_X86_CPU_DEBUG and schedule it for rapid removal
CONFIG_X86_CPU_DEBUG really seems to be causing more problems than it
ever solved. This is an RFC for immediately deprecating it, and
schedule it for removal in the 2.6.34 cycle.
If this was a high value feature, it would be different -- but it's not
even close.
Posting this as an RFC just on the offchance someone actually depends on
this.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
View attachment "0001-x86-Mark-CONFIG_X86_CPU_DEBUG-for-rapid-deprecation.patch" of type "text/x-patch" (2927 bytes)
Powered by blists - more mailing lists