lkml.org 
[lkml]   [2009]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[patch 2/4] cpufreq: Mark policy_rwsem as going static in cpufreq.c wont be exported
    lock_policy_rwsem_* and unlock_policy_rwsem_* routines in cpufreq.c are
    currently exported to drivers. Improper use of those locks can
    result in deadlocks and it is better to keep the locks localized.
    Two previous in-kernel users of these interfaces (ondemand and conservative),
    do not use this interfaces any more. Schedule them for removal.

    Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    ---
    Documentation/feature-removal-schedule.txt | 10 ++++++++++
    1 files changed, 10 insertions(+), 0 deletions(-)

    diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
    index f8cd450..09e031c 100644
    --- a/Documentation/feature-removal-schedule.txt
    +++ b/Documentation/feature-removal-schedule.txt
    @@ -458,3 +458,13 @@ Why: Remove the old legacy 32bit machine check code. This has been
    but the old version has been kept around for easier testing. Note this
    doesn't impact the old P5 and WinChip machine check handlers.
    Who: Andi Kleen <andi@firstfloor.org>
    +
    +----------------------------
    +
    +What: lock_policy_rwsem_* and unlock_policy_rwsem_* will not be
    + exported interface anymore.
    +When: 2.6.33
    +Why: cpu_policy_rwsem has a new cleaner definition making it local to
    + cpufreq core and contained inside cpufreq.c. Other dependent
    + drivers should not use it in order to safely avoid lockdep issues.
    +Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    --
    1.6.0.6
    --



    \
     
     \ /
      Last update: 2009-07-03 02:31    [W:6.675 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site