On Tue, 2014-02-25 at 13:29 +0530, Deepthi Dharwar wrote:
We currently do not use smt-snooze-delay in the kernel.
The sysfs entries needs to be retained until we do a clean up
ppc64_cpu
util that uses these entries to determine SMT,
clean up patch for this has already been posted out by
On 02/24/2014 08:53 PM, Madhavan Srinivasan wrote:
On Saturday 22 February 2014 05:44 AM, Cody P Schafer wrote:
/sys/devices/system/cpu/cpu*/smt-snooze-delay was converted into a NOP
in commit 3fa8cad82b94d0bed002571bd246f2299ffc876b, and now does
nothing. Add a pr_warn() to convince any users
On Wed, 2014-02-26 at 09:40 +1100, Benjamin Herrenschmidt wrote:
On Tue, 2014-02-25 at 13:29 +0530, Deepthi Dharwar wrote:
We currently do not use smt-snooze-delay in the kernel.
The sysfs entries needs to be retained until we do a clean up
ppc64_cpu
util that uses these entries to
On Saturday 22 February 2014 05:44 AM, Cody P Schafer wrote:
/sys/devices/system/cpu/cpu*/smt-snooze-delay was converted into a NOP
in commit 3fa8cad82b94d0bed002571bd246f2299ffc876b, and now does
nothing. Add a pr_warn() to convince any users that they should stop
using it.
The commit
On 02/22/2014 05:44 AM, Cody P Schafer wrote:
/sys/devices/system/cpu/cpu*/smt-snooze-delay was converted into a NOP
in commit 3fa8cad82b94d0bed002571bd246f2299ffc876b, and now does
nothing. Add a pr_warn() to convince any users that they should stop
using it.
The commit message from the
/sys/devices/system/cpu/cpu*/smt-snooze-delay was converted into a NOP
in commit 3fa8cad82b94d0bed002571bd246f2299ffc876b, and now does
nothing. Add a pr_warn() to convince any users that they should stop
using it.
The commit message from the removing commit notes that this
functionality should