• Andi Kleen's avatar
    [CPUFREQ] Don't take semaphore in cpufreq_quick_get() · 9eb59573
    Andi Kleen authored
    I don't see any reason to take an expensive lock in cpufreq_quick_get()
    Reading policy->cur is a single atomic operation and after
    the lock is dropped again the state could change any time anyways.
    
    So don't take the lock in the first place.
    
    This also makes this function interrupt safe which is useful
    for some code of mine.
    Signed-off-by: default avatarAndi Kleen <ak@suse.de>
    Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
    Signed-off-by: default avatarDave Jones <davej@redhat.com>
    9eb59573
cpufreq.c 47 KB