2005-04-17 02:20:36 +04:00
/*
* linux / drivers / cpufreq / cpufreq . c
*
* Copyright ( C ) 2001 Russell King
* ( C ) 2002 - 2003 Dominik Brodowski < linux @ brodo . de >
*
2005-10-31 01:59:54 +03:00
* Oct 2005 - Ashok Raj < ashok . raj @ intel . com >
2006-02-28 08:43:23 +03:00
* Added handling for CPU hotplug
2006-03-05 11:37:23 +03:00
* Feb 2006 - Jacob Shin < jacob . shin @ amd . com >
* Fix handling for CPU hotplug - - affected CPUs
2005-10-31 01:59:54 +03:00
*
2005-04-17 02:20:36 +04:00
* This program is free software ; you can redistribute it and / or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation .
*
*/
2012-10-23 03:29:03 +04:00
# define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
2005-04-17 02:20:36 +04:00
# include <linux/kernel.h>
# include <linux/module.h>
# include <linux/init.h>
# include <linux/notifier.h>
# include <linux/cpufreq.h>
# include <linux/delay.h>
# include <linux/interrupt.h>
# include <linux/spinlock.h>
# include <linux/device.h>
# include <linux/slab.h>
# include <linux/cpu.h>
# include <linux/completion.h>
2006-01-14 02:54:22 +03:00
# include <linux/mutex.h>
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
# include <linux/syscore_ops.h>
2005-04-17 02:20:36 +04:00
2010-04-20 15:17:36 +04:00
# include <trace/events/power.h>
2005-04-17 02:20:36 +04:00
/**
2006-08-12 01:59:28 +04:00
* The " cpufreq driver " - the arch - or hardware - dependent low
2005-04-17 02:20:36 +04:00
* level driver of CPUFreq support , and its spinlock . This lock
* also protects the cpufreq_cpu_data array .
*/
2006-02-03 01:03:42 +03:00
static struct cpufreq_driver * cpufreq_driver ;
2008-03-26 01:06:53 +03:00
static DEFINE_PER_CPU ( struct cpufreq_policy * , cpufreq_cpu_data ) ;
2007-07-09 22:35:28 +04:00
# ifdef CONFIG_HOTPLUG_CPU
/* This one keeps track of the previously set governor of a removed CPU */
2009-10-05 00:38:55 +04:00
static DEFINE_PER_CPU ( char [ CPUFREQ_NAME_LEN ] , cpufreq_cpu_governor ) ;
2007-07-09 22:35:28 +04:00
# endif
2013-02-22 20:24:34 +04:00
static DEFINE_RWLOCK ( cpufreq_driver_lock ) ;
2005-04-17 02:20:36 +04:00
2007-02-06 03:12:44 +03:00
/*
* cpu_policy_rwsem is a per CPU reader - writer semaphore designed to cure
* all cpufreq / hotplug / workqueue / etc related lock issues .
*
* The rules for this semaphore :
* - Any routine that wants to read from the policy structure will
* do a down_read on this semaphore .
* - Any routine that will write to the policy structure and / or may take away
* the policy altogether ( eg . CPU hotplug ) , will hold this lock in write
* mode before doing so .
*
* Additional rules :
* - Governor routines that can be called in cpufreq hotplug path should not
* take this sem as top level hotplug notifier handler takes this .
2009-06-08 21:17:31 +04:00
* - Lock should not be held across
* __cpufreq_governor ( data , CPUFREQ_GOV_STOP ) ;
2007-02-06 03:12:44 +03:00
*/
2009-10-29 16:34:13 +03:00
static DEFINE_PER_CPU ( int , cpufreq_policy_cpu ) ;
2007-02-06 03:12:44 +03:00
static DEFINE_PER_CPU ( struct rw_semaphore , cpu_policy_rwsem ) ;
# define lock_policy_rwsem(mode, cpu) \
2013-02-07 14:08:42 +04:00
static int lock_policy_rwsem_ # # mode ( int cpu ) \
2007-02-06 03:12:44 +03:00
{ \
2009-10-29 16:34:13 +03:00
int policy_cpu = per_cpu ( cpufreq_policy_cpu , cpu ) ; \
2007-02-06 03:12:44 +03:00
BUG_ON ( policy_cpu = = - 1 ) ; \
down_ # # mode ( & per_cpu ( cpu_policy_rwsem , policy_cpu ) ) ; \
\
return 0 ; \
}
lock_policy_rwsem ( read , cpu ) ;
lock_policy_rwsem ( write , cpu ) ;
2013-02-07 14:08:42 +04:00
# define unlock_policy_rwsem(mode, cpu) \
static void unlock_policy_rwsem_ # # mode ( int cpu ) \
{ \
int policy_cpu = per_cpu ( cpufreq_policy_cpu , cpu ) ; \
BUG_ON ( policy_cpu = = - 1 ) ; \
up_ # # mode ( & per_cpu ( cpu_policy_rwsem , policy_cpu ) ) ; \
2007-02-06 03:12:44 +03:00
}
2013-02-07 14:08:42 +04:00
unlock_policy_rwsem ( read , cpu ) ;
unlock_policy_rwsem ( write , cpu ) ;
2007-02-06 03:12:44 +03:00
2005-04-17 02:20:36 +04:00
/* internal prototypes */
2009-01-18 09:37:11 +03:00
static int __cpufreq_governor ( struct cpufreq_policy * policy ,
unsigned int event ) ;
2007-02-06 03:12:44 +03:00
static unsigned int __cpufreq_get ( unsigned int cpu ) ;
2006-11-22 17:55:48 +03:00
static void handle_update ( struct work_struct * work ) ;
2005-04-17 02:20:36 +04:00
/**
2006-02-28 08:43:23 +03:00
* Two notifier lists : the " policy " list is involved in the
* validation process for a new CPU frequency policy ; the
2005-04-17 02:20:36 +04:00
* " transition " list for kernel code that needs to handle
* changes to devices when the CPU clock speed changes .
* The mutex locks both lists .
*/
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
static BLOCKING_NOTIFIER_HEAD ( cpufreq_policy_notifier_list ) ;
2006-10-04 13:17:06 +04:00
static struct srcu_notifier_head cpufreq_transition_notifier_list ;
2005-04-17 02:20:36 +04:00
2008-02-16 13:41:24 +03:00
static bool init_cpufreq_transition_notifier_list_called ;
2006-10-04 13:17:06 +04:00
static int __init init_cpufreq_transition_notifier_list ( void )
{
srcu_init_notifier_head ( & cpufreq_transition_notifier_list ) ;
2008-02-16 13:41:24 +03:00
init_cpufreq_transition_notifier_list_called = true ;
2006-10-04 13:17:06 +04:00
return 0 ;
}
2006-11-20 22:47:18 +03:00
pure_initcall ( init_cpufreq_transition_notifier_list ) ;
2005-04-17 02:20:36 +04:00
2012-03-14 03:18:39 +04:00
static int off __read_mostly ;
2012-10-26 02:51:32 +04:00
static int cpufreq_disabled ( void )
2012-03-14 03:18:39 +04:00
{
return off ;
}
void disable_cpufreq ( void )
{
off = 1 ;
}
2005-04-17 02:20:36 +04:00
static LIST_HEAD ( cpufreq_governor_list ) ;
2009-01-18 09:37:11 +03:00
static DEFINE_MUTEX ( cpufreq_governor_mutex ) ;
2005-04-17 02:20:36 +04:00
2013-03-27 19:58:58 +04:00
bool have_governor_per_policy ( void )
{
return cpufreq_driver - > have_governor_per_policy ;
}
2012-07-20 22:14:38 +04:00
static struct cpufreq_policy * __cpufreq_cpu_get ( unsigned int cpu , bool sysfs )
2005-04-17 02:20:36 +04:00
{
struct cpufreq_policy * data ;
unsigned long flags ;
2008-03-26 01:06:53 +03:00
if ( cpu > = nr_cpu_ids )
2005-04-17 02:20:36 +04:00
goto err_out ;
/* get the cpufreq driver */
2013-02-22 20:24:34 +04:00
read_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
if ( ! cpufreq_driver )
goto err_out_unlock ;
if ( ! try_module_get ( cpufreq_driver - > owner ) )
goto err_out_unlock ;
/* get the CPU */
2008-03-26 01:06:53 +03:00
data = per_cpu ( cpufreq_cpu_data , cpu ) ;
2005-04-17 02:20:36 +04:00
if ( ! data )
goto err_out_put_module ;
2012-07-20 22:14:38 +04:00
if ( ! sysfs & & ! kobject_get ( & data - > kobj ) )
2005-04-17 02:20:36 +04:00
goto err_out_put_module ;
2013-02-22 20:24:34 +04:00
read_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
return data ;
2006-02-03 01:03:42 +03:00
err_out_put_module :
2005-04-17 02:20:36 +04:00
module_put ( cpufreq_driver - > owner ) ;
2006-02-03 01:03:42 +03:00
err_out_unlock :
2013-02-22 20:24:34 +04:00
read_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2006-02-03 01:03:42 +03:00
err_out :
2005-04-17 02:20:36 +04:00
return NULL ;
}
2012-07-20 22:14:38 +04:00
struct cpufreq_policy * cpufreq_cpu_get ( unsigned int cpu )
{
2013-01-17 20:22:21 +04:00
if ( cpufreq_disabled ( ) )
return NULL ;
2012-07-20 22:14:38 +04:00
return __cpufreq_cpu_get ( cpu , false ) ;
}
2005-04-17 02:20:36 +04:00
EXPORT_SYMBOL_GPL ( cpufreq_cpu_get ) ;
2012-07-20 22:14:38 +04:00
static struct cpufreq_policy * cpufreq_cpu_get_sysfs ( unsigned int cpu )
{
return __cpufreq_cpu_get ( cpu , true ) ;
}
static void __cpufreq_cpu_put ( struct cpufreq_policy * data , bool sysfs )
{
if ( ! sysfs )
kobject_put ( & data - > kobj ) ;
module_put ( cpufreq_driver - > owner ) ;
}
2006-02-03 01:03:42 +03:00
2005-04-17 02:20:36 +04:00
void cpufreq_cpu_put ( struct cpufreq_policy * data )
{
2013-01-17 20:22:21 +04:00
if ( cpufreq_disabled ( ) )
return ;
2012-07-20 22:14:38 +04:00
__cpufreq_cpu_put ( data , false ) ;
2005-04-17 02:20:36 +04:00
}
EXPORT_SYMBOL_GPL ( cpufreq_cpu_put ) ;
2012-07-20 22:14:38 +04:00
static void cpufreq_cpu_put_sysfs ( struct cpufreq_policy * data )
{
__cpufreq_cpu_put ( data , true ) ;
}
2005-04-17 02:20:36 +04:00
/*********************************************************************
* EXTERNALLY AFFECTING FREQUENCY CHANGES *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/**
* adjust_jiffies - adjust the system " loops_per_jiffy "
*
* This function alters the system " loops_per_jiffy " for the clock
* speed change . Note that loops_per_jiffy cannot be updated on SMP
2006-02-28 08:43:23 +03:00
* systems as each CPU might be scaled differently . So , use the arch
2005-04-17 02:20:36 +04:00
* per - CPU loops_per_jiffy value wherever possible .
*/
# ifndef CONFIG_SMP
static unsigned long l_p_j_ref ;
static unsigned int l_p_j_ref_freq ;
2006-01-15 00:20:43 +03:00
static void adjust_jiffies ( unsigned long val , struct cpufreq_freqs * ci )
2005-04-17 02:20:36 +04:00
{
if ( ci - > flags & CPUFREQ_CONST_LOOPS )
return ;
if ( ! l_p_j_ref_freq ) {
l_p_j_ref = loops_per_jiffy ;
l_p_j_ref_freq = ci - > old ;
2011-03-27 17:04:46 +04:00
pr_debug ( " saving %lu as reference value for loops_per_jiffy; "
2006-10-26 14:50:58 +04:00
" freq is %u kHz \n " , l_p_j_ref , l_p_j_ref_freq ) ;
2005-04-17 02:20:36 +04:00
}
2012-01-04 09:22:46 +04:00
if ( ( val = = CPUFREQ_POSTCHANGE & & ci - > old ! = ci - > new ) | |
2005-04-29 18:40:12 +04:00
( val = = CPUFREQ_RESUMECHANGE | | val = = CPUFREQ_SUSPENDCHANGE ) ) {
2006-10-26 14:50:58 +04:00
loops_per_jiffy = cpufreq_scale ( l_p_j_ref , l_p_j_ref_freq ,
ci - > new ) ;
2011-03-27 17:04:46 +04:00
pr_debug ( " scaling loops_per_jiffy to %lu "
2006-10-26 14:50:58 +04:00
" for frequency %u kHz \n " , loops_per_jiffy , ci - > new ) ;
2005-04-17 02:20:36 +04:00
}
}
# else
2006-10-26 14:50:58 +04:00
static inline void adjust_jiffies ( unsigned long val , struct cpufreq_freqs * ci )
{
return ;
}
2005-04-17 02:20:36 +04:00
# endif
/**
2006-02-01 02:53:55 +03:00
* cpufreq_notify_transition - call notifier chain and adjust_jiffies
* on frequency transition .
2005-04-17 02:20:36 +04:00
*
2006-02-01 02:53:55 +03:00
* This function calls the transition notifiers and the " adjust_jiffies "
* function . It is called twice on all CPU frequency changes that have
2006-02-28 08:43:23 +03:00
* external effects .
2005-04-17 02:20:36 +04:00
*/
void cpufreq_notify_transition ( struct cpufreq_freqs * freqs , unsigned int state )
{
2006-02-01 02:53:55 +03:00
struct cpufreq_policy * policy ;
2013-02-07 09:25:00 +04:00
unsigned long flags ;
2006-02-01 02:53:55 +03:00
2005-04-17 02:20:36 +04:00
BUG_ON ( irqs_disabled ( ) ) ;
2013-01-17 20:22:21 +04:00
if ( cpufreq_disabled ( ) )
return ;
2005-04-17 02:20:36 +04:00
freqs - > flags = cpufreq_driver - > flags ;
2011-03-27 17:04:46 +04:00
pr_debug ( " notification %u of frequency transition to %u kHz \n " ,
2006-02-01 02:53:55 +03:00
state , freqs - > new ) ;
2005-04-17 02:20:36 +04:00
2013-02-22 20:24:34 +04:00
read_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2008-03-26 01:06:53 +03:00
policy = per_cpu ( cpufreq_cpu_data , freqs - > cpu ) ;
2013-02-22 20:24:34 +04:00
read_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2013-02-07 09:25:00 +04:00
2005-04-17 02:20:36 +04:00
switch ( state ) {
2006-02-01 02:53:55 +03:00
2005-04-17 02:20:36 +04:00
case CPUFREQ_PRECHANGE :
2006-02-28 08:43:23 +03:00
/* detect if the driver reported a value as "old frequency"
2006-02-01 02:53:55 +03:00
* which is not equal to what the cpufreq core thinks is
* " old frequency " .
2005-04-17 02:20:36 +04:00
*/
if ( ! ( cpufreq_driver - > flags & CPUFREQ_CONST_LOOPS ) ) {
2006-02-01 02:53:55 +03:00
if ( ( policy ) & & ( policy - > cpu = = freqs - > cpu ) & &
( policy - > cur ) & & ( policy - > cur ! = freqs - > old ) ) {
2011-03-27 17:04:46 +04:00
pr_debug ( " Warning: CPU frequency is "
2006-02-01 02:53:55 +03:00
" %u, cpufreq assumed %u kHz. \n " ,
freqs - > old , policy - > cur ) ;
freqs - > old = policy - > cur ;
2005-04-17 02:20:36 +04:00
}
}
2006-10-04 13:17:06 +04:00
srcu_notifier_call_chain ( & cpufreq_transition_notifier_list ,
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
CPUFREQ_PRECHANGE , freqs ) ;
2005-04-17 02:20:36 +04:00
adjust_jiffies ( CPUFREQ_PRECHANGE , freqs ) ;
break ;
2006-02-01 02:53:55 +03:00
2005-04-17 02:20:36 +04:00
case CPUFREQ_POSTCHANGE :
adjust_jiffies ( CPUFREQ_POSTCHANGE , freqs ) ;
2011-03-27 17:04:46 +04:00
pr_debug ( " FREQ: %lu - CPU: %lu " , ( unsigned long ) freqs - > new ,
2010-04-20 15:17:36 +04:00
( unsigned long ) freqs - > cpu ) ;
2011-01-03 19:50:44 +03:00
trace_cpu_frequency ( freqs - > new , freqs - > cpu ) ;
2006-10-04 13:17:06 +04:00
srcu_notifier_call_chain ( & cpufreq_transition_notifier_list ,
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
CPUFREQ_POSTCHANGE , freqs ) ;
2006-02-01 02:53:55 +03:00
if ( likely ( policy ) & & likely ( policy - > cpu = = freqs - > cpu ) )
policy - > cur = freqs - > new ;
2005-04-17 02:20:36 +04:00
break ;
}
}
EXPORT_SYMBOL_GPL ( cpufreq_notify_transition ) ;
/*********************************************************************
* SYSFS INTERFACE *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
2006-07-06 23:30:26 +04:00
static struct cpufreq_governor * __find_governor ( const char * str_governor )
{
struct cpufreq_governor * t ;
list_for_each_entry ( t , & cpufreq_governor_list , governor_list )
2009-01-18 09:37:11 +03:00
if ( ! strnicmp ( str_governor , t - > name , CPUFREQ_NAME_LEN ) )
2006-07-06 23:30:26 +04:00
return t ;
return NULL ;
}
2005-04-17 02:20:36 +04:00
/**
* cpufreq_parse_governor - parse a governor string
*/
2008-03-05 22:28:32 +03:00
static int cpufreq_parse_governor ( char * str_governor , unsigned int * policy ,
2005-04-17 02:20:36 +04:00
struct cpufreq_governor * * governor )
{
2006-07-06 23:30:26 +04:00
int err = - EINVAL ;
2005-04-17 02:20:36 +04:00
if ( ! cpufreq_driver )
2006-07-06 23:30:26 +04:00
goto out ;
2005-04-17 02:20:36 +04:00
if ( cpufreq_driver - > setpolicy ) {
if ( ! strnicmp ( str_governor , " performance " , CPUFREQ_NAME_LEN ) ) {
* policy = CPUFREQ_POLICY_PERFORMANCE ;
2006-07-06 23:30:26 +04:00
err = 0 ;
2006-10-26 14:50:58 +04:00
} else if ( ! strnicmp ( str_governor , " powersave " ,
CPUFREQ_NAME_LEN ) ) {
2005-04-17 02:20:36 +04:00
* policy = CPUFREQ_POLICY_POWERSAVE ;
2006-07-06 23:30:26 +04:00
err = 0 ;
2005-04-17 02:20:36 +04:00
}
2006-07-06 23:30:26 +04:00
} else if ( cpufreq_driver - > target ) {
2005-04-17 02:20:36 +04:00
struct cpufreq_governor * t ;
2006-07-06 23:30:26 +04:00
2006-01-14 02:54:22 +03:00
mutex_lock ( & cpufreq_governor_mutex ) ;
2006-07-06 23:30:26 +04:00
t = __find_governor ( str_governor ) ;
2006-07-06 23:32:01 +04:00
if ( t = = NULL ) {
2011-05-04 19:38:56 +04:00
int ret ;
2006-07-06 23:32:01 +04:00
2011-05-04 19:38:56 +04:00
mutex_unlock ( & cpufreq_governor_mutex ) ;
ret = request_module ( " cpufreq_%s " , str_governor ) ;
mutex_lock ( & cpufreq_governor_mutex ) ;
2006-07-06 23:32:01 +04:00
2011-05-04 19:38:56 +04:00
if ( ret = = 0 )
t = __find_governor ( str_governor ) ;
2006-07-06 23:32:01 +04:00
}
2006-07-06 23:30:26 +04:00
if ( t ! = NULL ) {
* governor = t ;
err = 0 ;
2005-04-17 02:20:36 +04:00
}
2006-07-06 23:30:26 +04:00
2006-01-14 02:54:22 +03:00
mutex_unlock ( & cpufreq_governor_mutex ) ;
2005-04-17 02:20:36 +04:00
}
2009-01-18 09:37:11 +03:00
out :
2006-07-06 23:30:26 +04:00
return err ;
2005-04-17 02:20:36 +04:00
}
/**
2006-10-26 14:50:58 +04:00
* cpufreq_per_cpu_attr_read ( ) / show_ # # file_name ( ) -
* print out cpufreq information
2005-04-17 02:20:36 +04:00
*
* Write out information from cpufreq_driver - > policy [ cpu ] ; object must be
* " unsigned int " .
*/
2006-02-28 08:43:23 +03:00
# define show_one(file_name, object) \
static ssize_t show_ # # file_name \
2008-03-05 22:28:32 +03:00
( struct cpufreq_policy * policy , char * buf ) \
2006-02-28 08:43:23 +03:00
{ \
2009-01-18 09:37:11 +03:00
return sprintf ( buf , " %u \n " , policy - > object ) ; \
2005-04-17 02:20:36 +04:00
}
show_one ( cpuinfo_min_freq , cpuinfo . min_freq ) ;
show_one ( cpuinfo_max_freq , cpuinfo . max_freq ) ;
2009-02-04 03:17:41 +03:00
show_one ( cpuinfo_transition_latency , cpuinfo . transition_latency ) ;
2005-04-17 02:20:36 +04:00
show_one ( scaling_min_freq , min ) ;
show_one ( scaling_max_freq , max ) ;
show_one ( scaling_cur_freq , cur ) ;
2006-10-26 14:50:58 +04:00
static int __cpufreq_set_policy ( struct cpufreq_policy * data ,
struct cpufreq_policy * policy ) ;
2006-04-13 17:14:04 +04:00
2005-04-17 02:20:36 +04:00
/**
* cpufreq_per_cpu_attr_write ( ) / store_ # # file_name ( ) - sysfs write access
*/
# define store_one(file_name, object) \
static ssize_t store_ # # file_name \
2008-03-05 22:28:32 +03:00
( struct cpufreq_policy * policy , const char * buf , size_t count ) \
2005-04-17 02:20:36 +04:00
{ \
2012-10-31 09:49:13 +04:00
unsigned int ret ; \
2005-04-17 02:20:36 +04:00
struct cpufreq_policy new_policy ; \
\
ret = cpufreq_get_policy ( & new_policy , policy - > cpu ) ; \
if ( ret ) \
return - EINVAL ; \
\
2009-01-18 09:37:11 +03:00
ret = sscanf ( buf , " %u " , & new_policy . object ) ; \
2005-04-17 02:20:36 +04:00
if ( ret ! = 1 ) \
return - EINVAL ; \
\
2006-04-13 17:14:04 +04:00
ret = __cpufreq_set_policy ( policy , & new_policy ) ; \
policy - > user_policy . object = policy - > object ; \
2005-04-17 02:20:36 +04:00
\
return ret ? ret : count ; \
}
2009-01-18 09:37:11 +03:00
store_one ( scaling_min_freq , min ) ;
store_one ( scaling_max_freq , max ) ;
2005-04-17 02:20:36 +04:00
/**
* show_cpuinfo_cur_freq - current CPU frequency as detected by hardware
*/
2008-03-05 22:28:32 +03:00
static ssize_t show_cpuinfo_cur_freq ( struct cpufreq_policy * policy ,
char * buf )
2005-04-17 02:20:36 +04:00
{
2007-02-06 03:12:44 +03:00
unsigned int cur_freq = __cpufreq_get ( policy - > cpu ) ;
2005-04-17 02:20:36 +04:00
if ( ! cur_freq )
return sprintf ( buf , " <unknown> " ) ;
return sprintf ( buf , " %u \n " , cur_freq ) ;
}
/**
* show_scaling_governor - show the current policy for the specified CPU
*/
2008-03-05 22:28:32 +03:00
static ssize_t show_scaling_governor ( struct cpufreq_policy * policy , char * buf )
2005-04-17 02:20:36 +04:00
{
2009-01-18 09:37:11 +03:00
if ( policy - > policy = = CPUFREQ_POLICY_POWERSAVE )
2005-04-17 02:20:36 +04:00
return sprintf ( buf , " powersave \n " ) ;
else if ( policy - > policy = = CPUFREQ_POLICY_PERFORMANCE )
return sprintf ( buf , " performance \n " ) ;
else if ( policy - > governor )
2012-10-23 03:23:43 +04:00
return scnprintf ( buf , CPUFREQ_NAME_PLEN , " %s \n " ,
2009-01-18 09:37:11 +03:00
policy - > governor - > name ) ;
2005-04-17 02:20:36 +04:00
return - EINVAL ;
}
/**
* store_scaling_governor - store policy for the specified CPU
*/
2008-03-05 22:28:32 +03:00
static ssize_t store_scaling_governor ( struct cpufreq_policy * policy ,
const char * buf , size_t count )
2005-04-17 02:20:36 +04:00
{
2012-10-31 09:49:13 +04:00
unsigned int ret ;
2005-04-17 02:20:36 +04:00
char str_governor [ 16 ] ;
struct cpufreq_policy new_policy ;
ret = cpufreq_get_policy ( & new_policy , policy - > cpu ) ;
if ( ret )
return ret ;
2009-01-18 09:37:11 +03:00
ret = sscanf ( buf , " %15s " , str_governor ) ;
2005-04-17 02:20:36 +04:00
if ( ret ! = 1 )
return - EINVAL ;
2006-10-26 14:50:58 +04:00
if ( cpufreq_parse_governor ( str_governor , & new_policy . policy ,
& new_policy . governor ) )
2005-04-17 02:20:36 +04:00
return - EINVAL ;
2006-04-13 17:14:04 +04:00
/* Do not use cpufreq_set_policy here or the user_policy.max
will be wrongly overridden */
ret = __cpufreq_set_policy ( policy , & new_policy ) ;
policy - > user_policy . policy = policy - > policy ;
policy - > user_policy . governor = policy - > governor ;
2006-10-26 14:50:58 +04:00
if ( ret )
return ret ;
else
return count ;
2005-04-17 02:20:36 +04:00
}
/**
* show_scaling_driver - show the cpufreq driver currently loaded
*/
2008-03-05 22:28:32 +03:00
static ssize_t show_scaling_driver ( struct cpufreq_policy * policy , char * buf )
2005-04-17 02:20:36 +04:00
{
2012-10-23 03:23:43 +04:00
return scnprintf ( buf , CPUFREQ_NAME_PLEN , " %s \n " , cpufreq_driver - > name ) ;
2005-04-17 02:20:36 +04:00
}
/**
* show_scaling_available_governors - show the available CPUfreq governors
*/
2008-03-05 22:28:32 +03:00
static ssize_t show_scaling_available_governors ( struct cpufreq_policy * policy ,
char * buf )
2005-04-17 02:20:36 +04:00
{
ssize_t i = 0 ;
struct cpufreq_governor * t ;
if ( ! cpufreq_driver - > target ) {
i + = sprintf ( buf , " performance powersave " ) ;
goto out ;
}
list_for_each_entry ( t , & cpufreq_governor_list , governor_list ) {
2009-01-18 09:37:11 +03:00
if ( i > = ( ssize_t ) ( ( PAGE_SIZE / sizeof ( char ) )
- ( CPUFREQ_NAME_LEN + 2 ) ) )
2005-04-17 02:20:36 +04:00
goto out ;
2012-10-23 03:23:43 +04:00
i + = scnprintf ( & buf [ i ] , CPUFREQ_NAME_PLEN , " %s " , t - > name ) ;
2005-04-17 02:20:36 +04:00
}
2006-02-03 01:03:42 +03:00
out :
2005-04-17 02:20:36 +04:00
i + = sprintf ( & buf [ i ] , " \n " ) ;
return i ;
}
2008-04-19 00:31:12 +04:00
2009-01-04 16:18:06 +03:00
static ssize_t show_cpus ( const struct cpumask * mask , char * buf )
2005-04-17 02:20:36 +04:00
{
ssize_t i = 0 ;
unsigned int cpu ;
2009-01-04 16:18:06 +03:00
for_each_cpu ( cpu , mask ) {
2005-04-17 02:20:36 +04:00
if ( i )
i + = scnprintf ( & buf [ i ] , ( PAGE_SIZE - i - 2 ) , " " ) ;
i + = scnprintf ( & buf [ i ] , ( PAGE_SIZE - i - 2 ) , " %u " , cpu ) ;
if ( i > = ( PAGE_SIZE - 5 ) )
2009-01-18 09:37:11 +03:00
break ;
2005-04-17 02:20:36 +04:00
}
i + = sprintf ( & buf [ i ] , " \n " ) ;
return i ;
}
2008-04-19 00:31:12 +04:00
/**
* show_related_cpus - show the CPUs affected by each transition even if
* hw coordination is in use
*/
static ssize_t show_related_cpus ( struct cpufreq_policy * policy , char * buf )
{
return show_cpus ( policy - > related_cpus , buf ) ;
}
/**
* show_affected_cpus - show the CPUs affected by each transition
*/
static ssize_t show_affected_cpus ( struct cpufreq_policy * policy , char * buf )
{
return show_cpus ( policy - > cpus , buf ) ;
}
2007-10-26 21:18:21 +04:00
static ssize_t store_scaling_setspeed ( struct cpufreq_policy * policy ,
2008-03-05 22:28:32 +03:00
const char * buf , size_t count )
2007-10-26 21:18:21 +04:00
{
unsigned int freq = 0 ;
unsigned int ret ;
2008-06-06 09:46:33 +04:00
if ( ! policy - > governor | | ! policy - > governor - > store_setspeed )
2007-10-26 21:18:21 +04:00
return - EINVAL ;
ret = sscanf ( buf , " %u " , & freq ) ;
if ( ret ! = 1 )
return - EINVAL ;
policy - > governor - > store_setspeed ( policy , freq ) ;
return count ;
}
static ssize_t show_scaling_setspeed ( struct cpufreq_policy * policy , char * buf )
{
2008-06-06 09:46:33 +04:00
if ( ! policy - > governor | | ! policy - > governor - > show_setspeed )
2007-10-26 21:18:21 +04:00
return sprintf ( buf , " <unsupported> \n " ) ;
return policy - > governor - > show_setspeed ( policy , buf ) ;
}
2005-04-17 02:20:36 +04:00
2009-11-19 14:31:01 +03:00
/**
2012-10-23 03:23:33 +04:00
* show_bios_limit - show the current cpufreq HW / BIOS limitation
2009-11-19 14:31:01 +03:00
*/
static ssize_t show_bios_limit ( struct cpufreq_policy * policy , char * buf )
{
unsigned int limit ;
int ret ;
if ( cpufreq_driver - > bios_limit ) {
ret = cpufreq_driver - > bios_limit ( policy - > cpu , & limit ) ;
if ( ! ret )
return sprintf ( buf , " %u \n " , limit ) ;
}
return sprintf ( buf , " %u \n " , policy - > cpuinfo . max_freq ) ;
}
2010-03-31 23:56:46 +04:00
cpufreq_freq_attr_ro_perm ( cpuinfo_cur_freq , 0400 ) ;
cpufreq_freq_attr_ro ( cpuinfo_min_freq ) ;
cpufreq_freq_attr_ro ( cpuinfo_max_freq ) ;
cpufreq_freq_attr_ro ( cpuinfo_transition_latency ) ;
cpufreq_freq_attr_ro ( scaling_available_governors ) ;
cpufreq_freq_attr_ro ( scaling_driver ) ;
cpufreq_freq_attr_ro ( scaling_cur_freq ) ;
cpufreq_freq_attr_ro ( bios_limit ) ;
cpufreq_freq_attr_ro ( related_cpus ) ;
cpufreq_freq_attr_ro ( affected_cpus ) ;
cpufreq_freq_attr_rw ( scaling_min_freq ) ;
cpufreq_freq_attr_rw ( scaling_max_freq ) ;
cpufreq_freq_attr_rw ( scaling_governor ) ;
cpufreq_freq_attr_rw ( scaling_setspeed ) ;
2005-04-17 02:20:36 +04:00
2008-03-05 22:28:32 +03:00
static struct attribute * default_attrs [ ] = {
2005-04-17 02:20:36 +04:00
& cpuinfo_min_freq . attr ,
& cpuinfo_max_freq . attr ,
2009-02-04 03:17:41 +03:00
& cpuinfo_transition_latency . attr ,
2005-04-17 02:20:36 +04:00
& scaling_min_freq . attr ,
& scaling_max_freq . attr ,
& affected_cpus . attr ,
2008-04-19 00:31:12 +04:00
& related_cpus . attr ,
2005-04-17 02:20:36 +04:00
& scaling_governor . attr ,
& scaling_driver . attr ,
& scaling_available_governors . attr ,
2007-10-26 21:18:21 +04:00
& scaling_setspeed . attr ,
2005-04-17 02:20:36 +04:00
NULL
} ;
2009-07-24 17:25:05 +04:00
struct kobject * cpufreq_global_kobject ;
EXPORT_SYMBOL ( cpufreq_global_kobject ) ;
2009-01-18 09:37:11 +03:00
# define to_policy(k) container_of(k, struct cpufreq_policy, kobj)
# define to_attr(a) container_of(a, struct freq_attr, attr)
2005-04-17 02:20:36 +04:00
2009-01-18 09:37:11 +03:00
static ssize_t show ( struct kobject * kobj , struct attribute * attr , char * buf )
2005-04-17 02:20:36 +04:00
{
2008-03-05 22:28:32 +03:00
struct cpufreq_policy * policy = to_policy ( kobj ) ;
struct freq_attr * fattr = to_attr ( attr ) ;
2008-03-05 22:20:57 +03:00
ssize_t ret = - EINVAL ;
2012-07-20 22:14:38 +04:00
policy = cpufreq_cpu_get_sysfs ( policy - > cpu ) ;
2005-04-17 02:20:36 +04:00
if ( ! policy )
2008-03-05 22:20:57 +03:00
goto no_policy ;
2007-02-06 03:12:44 +03:00
if ( lock_policy_rwsem_read ( policy - > cpu ) < 0 )
2008-03-05 22:20:57 +03:00
goto fail ;
2007-02-06 03:12:44 +03:00
2006-10-26 14:50:58 +04:00
if ( fattr - > show )
ret = fattr - > show ( policy , buf ) ;
else
ret = - EIO ;
2007-02-06 03:12:44 +03:00
unlock_policy_rwsem_read ( policy - > cpu ) ;
2008-03-05 22:20:57 +03:00
fail :
2012-07-20 22:14:38 +04:00
cpufreq_cpu_put_sysfs ( policy ) ;
2008-03-05 22:20:57 +03:00
no_policy :
2005-04-17 02:20:36 +04:00
return ret ;
}
2008-03-05 22:28:32 +03:00
static ssize_t store ( struct kobject * kobj , struct attribute * attr ,
const char * buf , size_t count )
2005-04-17 02:20:36 +04:00
{
2008-03-05 22:28:32 +03:00
struct cpufreq_policy * policy = to_policy ( kobj ) ;
struct freq_attr * fattr = to_attr ( attr ) ;
2008-03-05 22:22:25 +03:00
ssize_t ret = - EINVAL ;
2012-07-20 22:14:38 +04:00
policy = cpufreq_cpu_get_sysfs ( policy - > cpu ) ;
2005-04-17 02:20:36 +04:00
if ( ! policy )
2008-03-05 22:22:25 +03:00
goto no_policy ;
2007-02-06 03:12:44 +03:00
if ( lock_policy_rwsem_write ( policy - > cpu ) < 0 )
2008-03-05 22:22:25 +03:00
goto fail ;
2007-02-06 03:12:44 +03:00
2006-10-26 14:50:58 +04:00
if ( fattr - > store )
ret = fattr - > store ( policy , buf , count ) ;
else
ret = - EIO ;
2007-02-06 03:12:44 +03:00
unlock_policy_rwsem_write ( policy - > cpu ) ;
2008-03-05 22:22:25 +03:00
fail :
2012-07-20 22:14:38 +04:00
cpufreq_cpu_put_sysfs ( policy ) ;
2008-03-05 22:22:25 +03:00
no_policy :
2005-04-17 02:20:36 +04:00
return ret ;
}
2008-03-05 22:28:32 +03:00
static void cpufreq_sysfs_release ( struct kobject * kobj )
2005-04-17 02:20:36 +04:00
{
2008-03-05 22:28:32 +03:00
struct cpufreq_policy * policy = to_policy ( kobj ) ;
2011-03-27 17:04:46 +04:00
pr_debug ( " last reference is dropped \n " ) ;
2005-04-17 02:20:36 +04:00
complete ( & policy - > kobj_unregister ) ;
}
2010-01-19 04:58:23 +03:00
static const struct sysfs_ops sysfs_ops = {
2005-04-17 02:20:36 +04:00
. show = show ,
. store = store ,
} ;
static struct kobj_type ktype_cpufreq = {
. sysfs_ops = & sysfs_ops ,
. default_attrs = default_attrs ,
. release = cpufreq_sysfs_release ,
} ;
2009-07-09 01:35:39 +04:00
/* symlink affected CPUs */
2009-11-18 06:27:08 +03:00
static int cpufreq_add_dev_symlink ( unsigned int cpu ,
struct cpufreq_policy * policy )
2009-07-09 01:35:39 +04:00
{
unsigned int j ;
int ret = 0 ;
for_each_cpu ( j , policy - > cpus ) {
struct cpufreq_policy * managed_policy ;
2011-12-22 02:29:42 +04:00
struct device * cpu_dev ;
2009-07-09 01:35:39 +04:00
if ( j = = cpu )
continue ;
2011-03-27 17:04:46 +04:00
pr_debug ( " CPU %u already managed, adding link \n " , j ) ;
2009-07-09 01:35:39 +04:00
managed_policy = cpufreq_cpu_get ( cpu ) ;
2011-12-22 02:29:42 +04:00
cpu_dev = get_cpu_device ( j ) ;
ret = sysfs_create_link ( & cpu_dev - > kobj , & policy - > kobj ,
2009-07-09 01:35:39 +04:00
" cpufreq " ) ;
if ( ret ) {
cpufreq_cpu_put ( managed_policy ) ;
return ret ;
}
}
return ret ;
}
2009-11-18 06:27:08 +03:00
static int cpufreq_add_dev_interface ( unsigned int cpu ,
struct cpufreq_policy * policy ,
2011-12-22 02:29:42 +04:00
struct device * dev )
2009-07-09 02:05:42 +04:00
{
2009-07-09 02:48:47 +04:00
struct cpufreq_policy new_policy ;
2009-07-09 02:05:42 +04:00
struct freq_attr * * drv_attr ;
unsigned long flags ;
int ret = 0 ;
unsigned int j ;
/* prepare interface data */
ret = kobject_init_and_add ( & policy - > kobj , & ktype_cpufreq ,
2011-12-22 02:29:42 +04:00
& dev - > kobj , " cpufreq " ) ;
2009-07-09 02:05:42 +04:00
if ( ret )
return ret ;
/* set up files for this cpu device */
drv_attr = cpufreq_driver - > attr ;
while ( ( drv_attr ) & & ( * drv_attr ) ) {
ret = sysfs_create_file ( & policy - > kobj , & ( ( * drv_attr ) - > attr ) ) ;
if ( ret )
goto err_out_kobj_put ;
drv_attr + + ;
}
if ( cpufreq_driver - > get ) {
ret = sysfs_create_file ( & policy - > kobj , & cpuinfo_cur_freq . attr ) ;
if ( ret )
goto err_out_kobj_put ;
}
if ( cpufreq_driver - > target ) {
ret = sysfs_create_file ( & policy - > kobj , & scaling_cur_freq . attr ) ;
if ( ret )
goto err_out_kobj_put ;
}
2009-11-19 14:31:01 +03:00
if ( cpufreq_driver - > bios_limit ) {
ret = sysfs_create_file ( & policy - > kobj , & bios_limit . attr ) ;
if ( ret )
goto err_out_kobj_put ;
}
2009-07-09 02:05:42 +04:00
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2009-07-09 02:05:42 +04:00
for_each_cpu ( j , policy - > cpus ) {
per_cpu ( cpufreq_cpu_data , j ) = policy ;
2009-10-29 16:34:13 +03:00
per_cpu ( cpufreq_policy_cpu , j ) = policy - > cpu ;
2009-07-09 02:05:42 +04:00
}
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2009-07-09 02:05:42 +04:00
ret = cpufreq_add_dev_symlink ( cpu , policy ) ;
2009-07-09 02:48:47 +04:00
if ( ret )
goto err_out_kobj_put ;
memcpy ( & new_policy , policy , sizeof ( struct cpufreq_policy ) ) ;
/* assure that the starting sequence is run in __cpufreq_set_policy */
policy - > governor = NULL ;
/* set default policy */
ret = __cpufreq_set_policy ( policy , & new_policy ) ;
policy - > user_policy . policy = policy - > policy ;
policy - > user_policy . governor = policy - > governor ;
if ( ret ) {
2011-03-27 17:04:46 +04:00
pr_debug ( " setting policy failed \n " ) ;
2009-07-09 02:48:47 +04:00
if ( cpufreq_driver - > exit )
cpufreq_driver - > exit ( policy ) ;
}
2009-07-09 02:05:42 +04:00
return ret ;
err_out_kobj_put :
kobject_put ( & policy - > kobj ) ;
wait_for_completion ( & policy - > kobj_unregister ) ;
return ret ;
}
2013-01-29 18:39:08 +04:00
# ifdef CONFIG_HOTPLUG_CPU
static int cpufreq_add_policy_cpu ( unsigned int cpu , unsigned int sibling ,
struct device * dev )
{
struct cpufreq_policy * policy ;
int ret = 0 ;
unsigned long flags ;
policy = cpufreq_cpu_get ( sibling ) ;
WARN_ON ( ! policy ) ;
__cpufreq_governor ( policy , CPUFREQ_GOV_STOP ) ;
2013-02-07 09:25:00 +04:00
lock_policy_rwsem_write ( sibling ) ;
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2013-02-07 09:25:00 +04:00
2013-01-29 18:39:08 +04:00
cpumask_set_cpu ( cpu , policy - > cpus ) ;
2013-02-07 09:25:00 +04:00
per_cpu ( cpufreq_policy_cpu , cpu ) = policy - > cpu ;
2013-01-29 18:39:08 +04:00
per_cpu ( cpufreq_cpu_data , cpu ) = policy ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2013-01-29 18:39:08 +04:00
2013-02-07 09:25:00 +04:00
unlock_policy_rwsem_write ( sibling ) ;
2013-01-29 18:39:08 +04:00
__cpufreq_governor ( policy , CPUFREQ_GOV_START ) ;
__cpufreq_governor ( policy , CPUFREQ_GOV_LIMITS ) ;
ret = sysfs_create_link ( & dev - > kobj , & policy - > kobj , " cpufreq " ) ;
if ( ret ) {
cpufreq_cpu_put ( policy ) ;
return ret ;
}
return 0 ;
}
# endif
2005-04-17 02:20:36 +04:00
/**
* cpufreq_add_dev - add a CPU device
*
2006-02-28 08:43:23 +03:00
* Adds the cpufreq interface for a CPU device .
2009-07-03 19:25:16 +04:00
*
* The Oracle says : try running cpufreq registration / unregistration concurrently
* with with cpu hotplugging and all hell will break loose . Tried to clean this
* mess up , but more thorough testing is needed . - Mathieu
2005-04-17 02:20:36 +04:00
*/
2011-12-22 02:29:42 +04:00
static int cpufreq_add_dev ( struct device * dev , struct subsys_interface * sif )
2005-04-17 02:20:36 +04:00
{
2013-01-29 18:39:08 +04:00
unsigned int j , cpu = dev - > id ;
2013-02-07 09:26:03 +04:00
int ret = - ENOMEM ;
2005-04-17 02:20:36 +04:00
struct cpufreq_policy * policy ;
unsigned long flags ;
2009-11-12 17:18:46 +03:00
# ifdef CONFIG_HOTPLUG_CPU
2013-01-29 18:39:08 +04:00
struct cpufreq_governor * gov ;
2009-11-12 17:18:46 +03:00
int sibling ;
# endif
2005-04-17 02:20:36 +04:00
2005-10-31 01:59:54 +03:00
if ( cpu_is_offline ( cpu ) )
return 0 ;
2011-03-27 17:04:46 +04:00
pr_debug ( " adding CPU %u \n " , cpu ) ;
2005-04-17 02:20:36 +04:00
# ifdef CONFIG_SMP
/* check whether a different CPU already registered this
* CPU because it is in the same boat . */
policy = cpufreq_cpu_get ( cpu ) ;
if ( unlikely ( policy ) ) {
2006-03-05 11:37:23 +03:00
cpufreq_cpu_put ( policy ) ;
2005-04-17 02:20:36 +04:00
return 0 ;
}
2013-01-29 18:39:08 +04:00
# ifdef CONFIG_HOTPLUG_CPU
/* Check if this cpu was hot-unplugged earlier and has siblings */
2013-02-22 20:24:34 +04:00
read_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2013-01-29 18:39:08 +04:00
for_each_online_cpu ( sibling ) {
struct cpufreq_policy * cp = per_cpu ( cpufreq_cpu_data , sibling ) ;
2013-02-07 09:25:00 +04:00
if ( cp & & cpumask_test_cpu ( cpu , cp - > related_cpus ) ) {
2013-02-22 20:24:34 +04:00
read_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2013-01-29 18:39:08 +04:00
return cpufreq_add_policy_cpu ( cpu , sibling , dev ) ;
2013-02-07 09:25:00 +04:00
}
2013-01-29 18:39:08 +04:00
}
2013-02-22 20:24:34 +04:00
read_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2013-01-29 18:39:08 +04:00
# endif
2005-04-17 02:20:36 +04:00
# endif
if ( ! try_module_get ( cpufreq_driver - > owner ) ) {
ret = - EINVAL ;
goto module_out ;
}
2005-10-21 02:17:43 +04:00
policy = kzalloc ( sizeof ( struct cpufreq_policy ) , GFP_KERNEL ) ;
2009-07-09 00:30:03 +04:00
if ( ! policy )
2005-04-17 02:20:36 +04:00
goto nomem_out ;
2009-07-09 00:30:03 +04:00
if ( ! alloc_cpumask_var ( & policy - > cpus , GFP_KERNEL ) )
2009-07-03 19:25:16 +04:00
goto err_free_policy ;
2009-07-09 00:30:03 +04:00
if ( ! zalloc_cpumask_var ( & policy - > related_cpus , GFP_KERNEL ) )
2009-07-03 19:25:16 +04:00
goto err_free_cpumask ;
2005-04-17 02:20:36 +04:00
policy - > cpu = cpu ;
2013-02-07 09:26:03 +04:00
policy - > governor = CPUFREQ_DEFAULT_GOVERNOR ;
2009-01-04 16:18:06 +03:00
cpumask_copy ( policy - > cpus , cpumask_of ( cpu ) ) ;
2005-04-17 02:20:36 +04:00
2007-02-06 03:12:44 +03:00
/* Initially set CPU itself as the policy_cpu */
2009-10-29 16:34:13 +03:00
per_cpu ( cpufreq_policy_cpu , cpu ) = cpu ;
2007-02-06 03:12:44 +03:00
2005-04-17 02:20:36 +04:00
init_completion ( & policy - > kobj_unregister ) ;
2006-11-22 17:55:48 +03:00
INIT_WORK ( & policy - > update , handle_update ) ;
2005-04-17 02:20:36 +04:00
/* call driver. From then on the cpufreq must be able
* to accept all calls to - > verify and - > setpolicy for this CPU
*/
ret = cpufreq_driver - > init ( policy ) ;
if ( ret ) {
2011-03-27 17:04:46 +04:00
pr_debug ( " initialization failed \n " ) ;
2013-02-07 09:25:00 +04:00
goto err_set_policy_cpu ;
2005-04-17 02:20:36 +04:00
}
2013-01-12 09:14:38 +04:00
2013-01-29 18:39:08 +04:00
/* related cpus should atleast have policy->cpus */
cpumask_or ( policy - > related_cpus , policy - > related_cpus , policy - > cpus ) ;
2013-01-12 09:14:38 +04:00
/*
* affected cpus must always be the one , which are online . We aren ' t
* managing offline cpus here .
*/
cpumask_and ( policy - > cpus , policy - > cpus , cpu_online_mask ) ;
2008-12-04 23:19:17 +03:00
policy - > user_policy . min = policy - > min ;
policy - > user_policy . max = policy - > max ;
2005-04-17 02:20:36 +04:00
2008-07-30 09:32:58 +04:00
blocking_notifier_call_chain ( & cpufreq_policy_notifier_list ,
CPUFREQ_START , policy ) ;
2013-01-29 18:39:08 +04:00
# ifdef CONFIG_HOTPLUG_CPU
gov = __find_governor ( per_cpu ( cpufreq_cpu_governor , cpu ) ) ;
if ( gov ) {
policy - > governor = gov ;
pr_debug ( " Restoring governor %s for cpu %d \n " ,
policy - > governor - > name , cpu ) ;
2009-07-24 17:25:03 +04:00
}
2013-01-29 18:39:08 +04:00
# endif
2005-04-17 02:20:36 +04:00
2011-12-22 02:29:42 +04:00
ret = cpufreq_add_dev_interface ( cpu , policy , dev ) ;
2009-07-09 01:35:39 +04:00
if ( ret )
goto err_out_unregister ;
2006-03-05 11:37:23 +03:00
2007-12-17 22:54:39 +03:00
kobject_uevent ( & policy - > kobj , KOBJ_ADD ) ;
2005-04-17 02:20:36 +04:00
module_put ( cpufreq_driver - > owner ) ;
2011-03-27 17:04:46 +04:00
pr_debug ( " initialization complete \n " ) ;
2006-03-29 10:48:37 +04:00
2005-04-17 02:20:36 +04:00
return 0 ;
err_out_unregister :
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2009-01-04 16:18:06 +03:00
for_each_cpu ( j , policy - > cpus )
2008-03-26 01:06:53 +03:00
per_cpu ( cpufreq_cpu_data , j ) = NULL ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
2007-12-20 19:13:05 +03:00
kobject_put ( & policy - > kobj ) ;
2005-04-17 02:20:36 +04:00
wait_for_completion ( & policy - > kobj_unregister ) ;
2013-02-07 09:25:00 +04:00
err_set_policy_cpu :
per_cpu ( cpufreq_policy_cpu , cpu ) = - 1 ;
2010-07-20 16:11:02 +04:00
free_cpumask_var ( policy - > related_cpus ) ;
2009-07-03 19:25:16 +04:00
err_free_cpumask :
free_cpumask_var ( policy - > cpus ) ;
err_free_policy :
2005-04-17 02:20:36 +04:00
kfree ( policy ) ;
nomem_out :
module_put ( cpufreq_driver - > owner ) ;
2005-10-31 01:59:54 +03:00
module_out :
2005-04-17 02:20:36 +04:00
return ret ;
}
2013-01-14 17:23:03 +04:00
static void update_policy_cpu ( struct cpufreq_policy * policy , unsigned int cpu )
{
int j ;
policy - > last_cpu = policy - > cpu ;
policy - > cpu = cpu ;
2013-02-04 15:38:51 +04:00
for_each_cpu ( j , policy - > cpus )
2013-01-14 17:23:03 +04:00
per_cpu ( cpufreq_policy_cpu , j ) = cpu ;
# ifdef CONFIG_CPU_FREQ_TABLE
cpufreq_frequency_table_update_policy_cpu ( policy ) ;
# endif
blocking_notifier_call_chain ( & cpufreq_policy_notifier_list ,
CPUFREQ_UPDATE_POLICY_CPU , policy ) ;
}
2005-04-17 02:20:36 +04:00
/**
2007-02-06 03:12:44 +03:00
* __cpufreq_remove_dev - remove a CPU device
2005-04-17 02:20:36 +04:00
*
* Removes the cpufreq interface for a CPU device .
2007-02-06 03:12:44 +03:00
* Caller should already have policy_rwsem in write mode for this CPU .
* This routine frees the rwsem before returning .
2005-04-17 02:20:36 +04:00
*/
2011-12-22 02:29:42 +04:00
static int __cpufreq_remove_dev ( struct device * dev , struct subsys_interface * sif )
2005-04-17 02:20:36 +04:00
{
2013-01-14 17:23:03 +04:00
unsigned int cpu = dev - > id , ret , cpus ;
2005-04-17 02:20:36 +04:00
unsigned long flags ;
struct cpufreq_policy * data ;
2010-03-04 11:23:46 +03:00
struct kobject * kobj ;
struct completion * cmp ;
2011-12-22 02:29:42 +04:00
struct device * cpu_dev ;
2005-04-17 02:20:36 +04:00
2013-01-14 17:23:03 +04:00
pr_debug ( " %s: unregistering CPU %u \n " , __func__ , cpu ) ;
2005-04-17 02:20:36 +04:00
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2013-02-07 09:25:00 +04:00
2008-03-26 01:06:53 +03:00
data = per_cpu ( cpufreq_cpu_data , cpu ) ;
2013-02-07 09:25:00 +04:00
per_cpu ( cpufreq_cpu_data , cpu ) = NULL ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
if ( ! data ) {
2013-01-14 17:23:03 +04:00
pr_debug ( " %s: No cpu_data found \n " , __func__ ) ;
2005-04-17 02:20:36 +04:00
return - EINVAL ;
}
2013-01-14 17:23:03 +04:00
if ( cpufreq_driver - > target )
2013-01-12 09:14:39 +04:00
__cpufreq_governor ( data , CPUFREQ_GOV_STOP ) ;
2005-04-17 02:20:36 +04:00
2007-07-09 22:35:28 +04:00
# ifdef CONFIG_HOTPLUG_CPU
2013-02-06 21:02:11 +04:00
if ( ! cpufreq_driver - > setpolicy )
strncpy ( per_cpu ( cpufreq_cpu_governor , cpu ) ,
data - > governor - > name , CPUFREQ_NAME_LEN ) ;
2005-04-17 02:20:36 +04:00
# endif
2013-02-07 09:25:00 +04:00
WARN_ON ( lock_policy_rwsem_write ( cpu ) ) ;
2013-01-14 17:23:03 +04:00
cpus = cpumask_weight ( data - > cpus ) ;
cpumask_clear_cpu ( cpu , data - > cpus ) ;
2013-02-07 09:25:00 +04:00
unlock_policy_rwsem_write ( cpu ) ;
2007-07-09 22:35:28 +04:00
2013-02-06 01:21:14 +04:00
if ( cpu ! = data - > cpu ) {
sysfs_remove_link ( & dev - > kobj , " cpufreq " ) ;
} else if ( cpus > 1 ) {
2013-01-14 17:23:03 +04:00
/* first sibling now owns the new sysfs dir */
cpu_dev = get_cpu_device ( cpumask_first ( data - > cpus ) ) ;
sysfs_remove_link ( & cpu_dev - > kobj , " cpufreq " ) ;
ret = kobject_move ( & data - > kobj , & cpu_dev - > kobj ) ;
if ( ret ) {
pr_err ( " %s: Failed to move kobj: %d " , __func__ , ret ) ;
2007-07-09 22:35:28 +04:00
2013-02-07 09:25:00 +04:00
WARN_ON ( lock_policy_rwsem_write ( cpu ) ) ;
2013-01-14 17:23:03 +04:00
cpumask_set_cpu ( cpu , data - > cpus ) ;
2005-04-17 02:20:36 +04:00
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2013-02-07 09:25:00 +04:00
per_cpu ( cpufreq_cpu_data , cpu ) = data ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
2010-03-04 11:23:46 +03:00
unlock_policy_rwsem_write ( cpu ) ;
2005-04-17 02:20:36 +04:00
2013-02-07 09:25:00 +04:00
ret = sysfs_create_link ( & cpu_dev - > kobj , & data - > kobj ,
" cpufreq " ) ;
2013-01-14 17:23:03 +04:00
return - EINVAL ;
2005-04-17 02:20:36 +04:00
}
2007-02-06 03:12:44 +03:00
2013-02-07 09:25:00 +04:00
WARN_ON ( lock_policy_rwsem_write ( cpu ) ) ;
2013-01-14 17:23:03 +04:00
update_policy_cpu ( data , cpu_dev - > id ) ;
2013-02-07 09:25:00 +04:00
unlock_policy_rwsem_write ( cpu ) ;
2013-01-14 17:23:03 +04:00
pr_debug ( " %s: policy Kobject moved to cpu: %d from: %d \n " ,
__func__ , cpu_dev - > id , cpu ) ;
2005-04-17 02:20:36 +04:00
}
2013-01-14 17:23:03 +04:00
pr_debug ( " %s: removing link, cpu: %d \n " , __func__ , cpu ) ;
cpufreq_cpu_put ( data ) ;
2005-04-17 02:20:36 +04:00
2013-01-14 17:23:03 +04:00
/* If cpu is last user of policy, free policy */
if ( cpus = = 1 ) {
2013-03-27 19:58:57 +04:00
__cpufreq_governor ( data , CPUFREQ_GOV_POLICY_EXIT ) ;
2013-02-07 09:25:00 +04:00
lock_policy_rwsem_read ( cpu ) ;
2013-01-14 17:23:03 +04:00
kobj = & data - > kobj ;
cmp = & data - > kobj_unregister ;
2013-02-07 09:25:00 +04:00
unlock_policy_rwsem_read ( cpu ) ;
2013-01-14 17:23:03 +04:00
kobject_put ( kobj ) ;
2009-07-03 04:08:30 +04:00
2013-01-14 17:23:03 +04:00
/* we need to make sure that the underlying kobj is actually
* not referenced anymore by anybody before we proceed with
* unloading .
*/
pr_debug ( " waiting for dropping of refcount \n " ) ;
wait_for_completion ( cmp ) ;
pr_debug ( " wait complete \n " ) ;
2009-07-03 04:08:30 +04:00
2013-01-14 17:23:03 +04:00
if ( cpufreq_driver - > exit )
cpufreq_driver - > exit ( data ) ;
[CPUFREQ] CPU hotplug, re-create sysfs directory and symlinks
When we discover CPUs that are affected by each other's
frequency/voltage transitions, the first CPU gets a sysfs directory
created, and rest of the siblings get symlinks. Currently, when we
hotplug off only the first CPU, all of the symlinks and the sysfs
directory gets removed. Even though rest of the siblings are still
online and functional, they are orphaned, and no longer governed by
cpufreq.
This patch, given the above scenario, creates a sysfs directory for
the first sibling and symlinks for the rest of the siblings.
Please note the recursive call, it was rather too ugly to roll it
out. And the removal of redundant NULL setting (it is already taken
care of near the top of the function).
Signed-off-by: Jacob Shin <jacob.shin@amd.com>
Acked-by: Mark Langsdorf <mark.langsdorf@amd.com>
Reviewed-by: Thomas Renninger <trenn@suse.de>
Signed-off-by: Dave Jones <davej@redhat.com>
Cc: stable@kernel.org
2011-04-27 22:32:11 +04:00
2013-01-14 17:23:03 +04:00
free_cpumask_var ( data - > related_cpus ) ;
free_cpumask_var ( data - > cpus ) ;
kfree ( data ) ;
} else if ( cpufreq_driver - > target ) {
__cpufreq_governor ( data , CPUFREQ_GOV_START ) ;
__cpufreq_governor ( data , CPUFREQ_GOV_LIMITS ) ;
[CPUFREQ] CPU hotplug, re-create sysfs directory and symlinks
When we discover CPUs that are affected by each other's
frequency/voltage transitions, the first CPU gets a sysfs directory
created, and rest of the siblings get symlinks. Currently, when we
hotplug off only the first CPU, all of the symlinks and the sysfs
directory gets removed. Even though rest of the siblings are still
online and functional, they are orphaned, and no longer governed by
cpufreq.
This patch, given the above scenario, creates a sysfs directory for
the first sibling and symlinks for the rest of the siblings.
Please note the recursive call, it was rather too ugly to roll it
out. And the removal of redundant NULL setting (it is already taken
care of near the top of the function).
Signed-off-by: Jacob Shin <jacob.shin@amd.com>
Acked-by: Mark Langsdorf <mark.langsdorf@amd.com>
Reviewed-by: Thomas Renninger <trenn@suse.de>
Signed-off-by: Dave Jones <davej@redhat.com>
Cc: stable@kernel.org
2011-04-27 22:32:11 +04:00
}
2005-04-17 02:20:36 +04:00
2013-02-07 09:25:00 +04:00
per_cpu ( cpufreq_policy_cpu , cpu ) = - 1 ;
2005-04-17 02:20:36 +04:00
return 0 ;
}
2011-12-22 02:29:42 +04:00
static int cpufreq_remove_dev ( struct device * dev , struct subsys_interface * sif )
2007-02-06 03:12:44 +03:00
{
2011-12-22 02:29:42 +04:00
unsigned int cpu = dev - > id ;
2007-02-06 03:12:44 +03:00
int retval ;
2007-03-26 23:03:19 +04:00
if ( cpu_is_offline ( cpu ) )
return 0 ;
2011-12-22 02:29:42 +04:00
retval = __cpufreq_remove_dev ( dev , sif ) ;
2007-02-06 03:12:44 +03:00
return retval ;
}
2006-11-22 17:55:48 +03:00
static void handle_update ( struct work_struct * work )
2005-04-17 02:20:36 +04:00
{
2006-11-22 17:55:48 +03:00
struct cpufreq_policy * policy =
container_of ( work , struct cpufreq_policy , update ) ;
unsigned int cpu = policy - > cpu ;
2011-03-27 17:04:46 +04:00
pr_debug ( " handle_update for cpu %u called \n " , cpu ) ;
2005-04-17 02:20:36 +04:00
cpufreq_update_policy ( cpu ) ;
}
/**
* cpufreq_out_of_sync - If actual and saved CPU frequency differs , we ' re in deep trouble .
* @ cpu : cpu number
* @ old_freq : CPU frequency the kernel thinks the CPU runs at
* @ new_freq : CPU frequency the CPU actually runs at
*
2009-01-18 09:37:11 +03:00
* We adjust to current frequency first , and need to clean up later .
* So either call to cpufreq_update_policy ( ) or schedule handle_update ( ) ) .
2005-04-17 02:20:36 +04:00
*/
2006-10-26 14:50:58 +04:00
static void cpufreq_out_of_sync ( unsigned int cpu , unsigned int old_freq ,
unsigned int new_freq )
2005-04-17 02:20:36 +04:00
{
struct cpufreq_freqs freqs ;
2011-03-27 17:04:46 +04:00
pr_debug ( " Warning: CPU frequency out of sync: cpufreq and timing "
2005-04-17 02:20:36 +04:00
" core thinks of %u, is %u kHz. \n " , old_freq , new_freq ) ;
freqs . cpu = cpu ;
freqs . old = old_freq ;
freqs . new = new_freq ;
cpufreq_notify_transition ( & freqs , CPUFREQ_PRECHANGE ) ;
cpufreq_notify_transition ( & freqs , CPUFREQ_POSTCHANGE ) ;
}
2006-02-28 08:43:23 +03:00
/**
2006-12-13 12:19:15 +03:00
* cpufreq_quick_get - get the CPU frequency ( in kHz ) from policy - > cur
2005-12-02 21:43:20 +03:00
* @ cpu : CPU number
*
* This is the last known freq , without actually getting it from the driver .
* Return value will be same as what is shown in scaling_cur_freq in sysfs .
*/
unsigned int cpufreq_quick_get ( unsigned int cpu )
{
2013-02-06 21:02:08 +04:00
struct cpufreq_policy * policy ;
2006-10-26 14:50:58 +04:00
unsigned int ret_freq = 0 ;
2005-12-02 21:43:20 +03:00
2013-02-06 21:02:08 +04:00
if ( cpufreq_driver & & cpufreq_driver - > setpolicy & & cpufreq_driver - > get )
return cpufreq_driver - > get ( cpu ) ;
policy = cpufreq_cpu_get ( cpu ) ;
2005-12-02 21:43:20 +03:00
if ( policy ) {
2006-10-26 14:50:58 +04:00
ret_freq = policy - > cur ;
2005-12-02 21:43:20 +03:00
cpufreq_cpu_put ( policy ) ;
}
2008-02-08 00:33:49 +03:00
return ret_freq ;
2005-12-02 21:43:20 +03:00
}
EXPORT_SYMBOL ( cpufreq_quick_get ) ;
2011-06-28 21:59:12 +04:00
/**
* cpufreq_quick_get_max - get the max reported CPU frequency for this CPU
* @ cpu : CPU number
*
* Just return the max possible frequency for a given CPU .
*/
unsigned int cpufreq_quick_get_max ( unsigned int cpu )
{
struct cpufreq_policy * policy = cpufreq_cpu_get ( cpu ) ;
unsigned int ret_freq = 0 ;
if ( policy ) {
ret_freq = policy - > max ;
cpufreq_cpu_put ( policy ) ;
}
return ret_freq ;
}
EXPORT_SYMBOL ( cpufreq_quick_get_max ) ;
2005-12-02 21:43:20 +03:00
2007-02-06 03:12:44 +03:00
static unsigned int __cpufreq_get ( unsigned int cpu )
2005-04-17 02:20:36 +04:00
{
2008-03-26 01:06:53 +03:00
struct cpufreq_policy * policy = per_cpu ( cpufreq_cpu_data , cpu ) ;
2006-10-26 14:50:58 +04:00
unsigned int ret_freq = 0 ;
2005-04-17 02:20:36 +04:00
if ( ! cpufreq_driver - > get )
2008-02-08 00:33:49 +03:00
return ret_freq ;
2005-04-17 02:20:36 +04:00
2006-10-26 14:50:58 +04:00
ret_freq = cpufreq_driver - > get ( cpu ) ;
2005-04-17 02:20:36 +04:00
2006-10-26 14:50:58 +04:00
if ( ret_freq & & policy - > cur & &
! ( cpufreq_driver - > flags & CPUFREQ_CONST_LOOPS ) ) {
/* verify no discrepancy between actual and
saved value exists */
if ( unlikely ( ret_freq ! = policy - > cur ) ) {
cpufreq_out_of_sync ( cpu , policy - > cur , ret_freq ) ;
2005-04-17 02:20:36 +04:00
schedule_work ( & policy - > update ) ;
}
}
2008-02-08 00:33:49 +03:00
return ret_freq ;
2007-02-06 03:12:44 +03:00
}
2005-04-17 02:20:36 +04:00
2007-02-06 03:12:44 +03:00
/**
* cpufreq_get - get the current CPU frequency ( in kHz )
* @ cpu : CPU number
*
* Get the CPU current ( static ) CPU frequency
*/
unsigned int cpufreq_get ( unsigned int cpu )
{
unsigned int ret_freq = 0 ;
struct cpufreq_policy * policy = cpufreq_cpu_get ( cpu ) ;
if ( ! policy )
goto out ;
if ( unlikely ( lock_policy_rwsem_read ( cpu ) ) )
goto out_policy ;
ret_freq = __cpufreq_get ( cpu ) ;
unlock_policy_rwsem_read ( cpu ) ;
2005-04-17 02:20:36 +04:00
2007-02-06 03:12:44 +03:00
out_policy :
cpufreq_cpu_put ( policy ) ;
out :
2008-02-08 00:33:49 +03:00
return ret_freq ;
2005-04-17 02:20:36 +04:00
}
EXPORT_SYMBOL ( cpufreq_get ) ;
2011-12-22 02:29:42 +04:00
static struct subsys_interface cpufreq_interface = {
. name = " cpufreq " ,
. subsys = & cpu_subsys ,
. add_dev = cpufreq_add_dev ,
. remove_dev = cpufreq_remove_dev ,
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
} ;
2005-04-17 02:20:36 +04:00
2005-04-29 18:40:12 +04:00
/**
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
* cpufreq_bp_suspend - Prepare the boot CPU for system suspend .
*
* This function is only executed for the boot processor . The other CPUs
* have been put offline by means of CPU hotplug .
2005-04-29 18:40:12 +04:00
*/
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
static int cpufreq_bp_suspend ( void )
2005-04-29 18:40:12 +04:00
{
2006-10-26 14:50:58 +04:00
int ret = 0 ;
2009-08-04 22:03:25 +04:00
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
int cpu = smp_processor_id ( ) ;
2005-04-29 18:40:12 +04:00
struct cpufreq_policy * cpu_policy ;
2011-03-27 17:04:46 +04:00
pr_debug ( " suspending cpu %u \n " , cpu ) ;
2005-04-29 18:40:12 +04:00
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
/* If there's no policy for the boot CPU, we have nothing to do. */
2005-04-29 18:40:12 +04:00
cpu_policy = cpufreq_cpu_get ( cpu ) ;
if ( ! cpu_policy )
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
return 0 ;
2005-04-29 18:40:12 +04:00
if ( cpufreq_driver - > suspend ) {
2011-03-10 23:13:05 +03:00
ret = cpufreq_driver - > suspend ( cpu_policy ) ;
[CPUFREQ] Re-enable cpufreq suspend and resume code
Commit 4bc5d3413503 is broken and causes regressions:
(1) cpufreq_driver->resume() and ->suspend() were only called on
__powerpc__, but you could set them on all architectures. In fact,
->resume() was defined and used before the PPC-related commit
42d4dc3f4e1e complained about in 4bc5d3413503.
(2) Therfore, the resume functions in acpi_cpufreq and speedstep-smi
would never be called.
(3) This means speedstep-smi would be unusuable after suspend or resume.
The _real_ problem was calling cpufreq_driver->get() with interrupts
off, but it re-enabling interrupts on some platforms. Why is ->get()
necessary?
Some systems like to change the CPU frequency behind our
back, especially during BIOS-intensive operations like suspend or
resume. If such systems also use a CPU frequency-dependant timing loop,
delays might be off by large factors. Therefore, we need to ascertain
as soon as possible that the CPU frequency is indeed at the speed we
think it is. You can do this two ways: either setting it anew, or trying
to get it. The latter is what was done, the former also has the same IRQ
issue.
So, let's try something different: defer the checking to after interrupts
are re-enabled, by calling cpufreq_update_policy() (via schedule_work()).
Timings may be off until this later stage, so let's watch out for
resume regressions caused by the deferred handling of frequency changes
behind the kernel's back.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Dave Jones <davej@redhat.com>
2009-08-08 00:58:51 +04:00
if ( ret )
2005-04-29 18:40:12 +04:00
printk ( KERN_ERR " cpufreq: suspend failed in ->suspend "
" step on CPU %u \n " , cpu_policy - > cpu ) ;
}
cpufreq_cpu_put ( cpu_policy ) ;
2008-02-08 00:32:18 +03:00
return ret ;
2005-04-29 18:40:12 +04:00
}
2005-04-17 02:20:36 +04:00
/**
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
* cpufreq_bp_resume - Restore proper frequency handling of the boot CPU .
2005-04-17 02:20:36 +04:00
*
* 1. ) resume CPUfreq hardware support ( cpufreq_driver - > resume ( ) )
[CPUFREQ] Re-enable cpufreq suspend and resume code
Commit 4bc5d3413503 is broken and causes regressions:
(1) cpufreq_driver->resume() and ->suspend() were only called on
__powerpc__, but you could set them on all architectures. In fact,
->resume() was defined and used before the PPC-related commit
42d4dc3f4e1e complained about in 4bc5d3413503.
(2) Therfore, the resume functions in acpi_cpufreq and speedstep-smi
would never be called.
(3) This means speedstep-smi would be unusuable after suspend or resume.
The _real_ problem was calling cpufreq_driver->get() with interrupts
off, but it re-enabling interrupts on some platforms. Why is ->get()
necessary?
Some systems like to change the CPU frequency behind our
back, especially during BIOS-intensive operations like suspend or
resume. If such systems also use a CPU frequency-dependant timing loop,
delays might be off by large factors. Therefore, we need to ascertain
as soon as possible that the CPU frequency is indeed at the speed we
think it is. You can do this two ways: either setting it anew, or trying
to get it. The latter is what was done, the former also has the same IRQ
issue.
So, let's try something different: defer the checking to after interrupts
are re-enabled, by calling cpufreq_update_policy() (via schedule_work()).
Timings may be off until this later stage, so let's watch out for
resume regressions caused by the deferred handling of frequency changes
behind the kernel's back.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Dave Jones <davej@redhat.com>
2009-08-08 00:58:51 +04:00
* 2. ) schedule call cpufreq_update_policy ( ) ASAP as interrupts are
* restored . It will verify that the current freq is in sync with
* what we believe it to be . This is a bit later than when it
* should be , but nonethteless it ' s better than calling
* cpufreq_driver - > get ( ) here which might re - enable interrupts . . .
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
*
* This function is only executed for the boot CPU . The other CPUs have not
* been turned on yet .
2005-04-17 02:20:36 +04:00
*/
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
static void cpufreq_bp_resume ( void )
2005-04-17 02:20:36 +04:00
{
2006-10-26 14:50:58 +04:00
int ret = 0 ;
2009-08-04 22:03:25 +04:00
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
int cpu = smp_processor_id ( ) ;
2005-04-17 02:20:36 +04:00
struct cpufreq_policy * cpu_policy ;
2011-03-27 17:04:46 +04:00
pr_debug ( " resuming cpu %u \n " , cpu ) ;
2005-04-17 02:20:36 +04:00
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
/* If there's no policy for the boot CPU, we have nothing to do. */
2005-04-17 02:20:36 +04:00
cpu_policy = cpufreq_cpu_get ( cpu ) ;
if ( ! cpu_policy )
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
return ;
2005-04-17 02:20:36 +04:00
if ( cpufreq_driver - > resume ) {
ret = cpufreq_driver - > resume ( cpu_policy ) ;
if ( ret ) {
printk ( KERN_ERR " cpufreq: resume failed in ->resume "
" step on CPU %u \n " , cpu_policy - > cpu ) ;
2008-02-08 00:32:18 +03:00
goto fail ;
2005-04-17 02:20:36 +04:00
}
}
schedule_work ( & cpu_policy - > update ) ;
[CPUFREQ] Re-enable cpufreq suspend and resume code
Commit 4bc5d3413503 is broken and causes regressions:
(1) cpufreq_driver->resume() and ->suspend() were only called on
__powerpc__, but you could set them on all architectures. In fact,
->resume() was defined and used before the PPC-related commit
42d4dc3f4e1e complained about in 4bc5d3413503.
(2) Therfore, the resume functions in acpi_cpufreq and speedstep-smi
would never be called.
(3) This means speedstep-smi would be unusuable after suspend or resume.
The _real_ problem was calling cpufreq_driver->get() with interrupts
off, but it re-enabling interrupts on some platforms. Why is ->get()
necessary?
Some systems like to change the CPU frequency behind our
back, especially during BIOS-intensive operations like suspend or
resume. If such systems also use a CPU frequency-dependant timing loop,
delays might be off by large factors. Therefore, we need to ascertain
as soon as possible that the CPU frequency is indeed at the speed we
think it is. You can do this two ways: either setting it anew, or trying
to get it. The latter is what was done, the former also has the same IRQ
issue.
So, let's try something different: defer the checking to after interrupts
are re-enabled, by calling cpufreq_update_policy() (via schedule_work()).
Timings may be off until this later stage, so let's watch out for
resume regressions caused by the deferred handling of frequency changes
behind the kernel's back.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Dave Jones <davej@redhat.com>
2009-08-08 00:58:51 +04:00
2008-02-08 00:32:18 +03:00
fail :
2005-04-17 02:20:36 +04:00
cpufreq_cpu_put ( cpu_policy ) ;
}
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
static struct syscore_ops cpufreq_syscore_ops = {
. suspend = cpufreq_bp_suspend ,
. resume = cpufreq_bp_resume ,
2005-04-17 02:20:36 +04:00
} ;
2013-01-20 14:24:28 +04:00
/**
* cpufreq_get_current_driver - return current driver ' s name
*
* Return the name string of the currently loaded cpufreq driver
* or NULL , if none .
*/
const char * cpufreq_get_current_driver ( void )
{
if ( cpufreq_driver )
return cpufreq_driver - > name ;
return NULL ;
}
EXPORT_SYMBOL_GPL ( cpufreq_get_current_driver ) ;
2005-04-17 02:20:36 +04:00
/*********************************************************************
* NOTIFIER LISTS INTERFACE *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/**
* cpufreq_register_notifier - register a driver with cpufreq
* @ nb : notifier function to register
* @ list : CPUFREQ_TRANSITION_NOTIFIER or CPUFREQ_POLICY_NOTIFIER
*
2006-02-28 08:43:23 +03:00
* Add a driver to one of two lists : either a list of drivers that
2005-04-17 02:20:36 +04:00
* are notified about clock rate changes ( once before and once after
* the transition ) , or a list of drivers that are notified about
* changes in cpufreq policy .
*
* This function may sleep , and has the same return conditions as
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
* blocking_notifier_chain_register .
2005-04-17 02:20:36 +04:00
*/
int cpufreq_register_notifier ( struct notifier_block * nb , unsigned int list )
{
int ret ;
2013-01-17 20:22:21 +04:00
if ( cpufreq_disabled ( ) )
return - EINVAL ;
2008-02-16 13:41:24 +03:00
WARN_ON ( ! init_cpufreq_transition_notifier_list_called ) ;
2005-04-17 02:20:36 +04:00
switch ( list ) {
case CPUFREQ_TRANSITION_NOTIFIER :
2006-10-04 13:17:06 +04:00
ret = srcu_notifier_chain_register (
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
& cpufreq_transition_notifier_list , nb ) ;
2005-04-17 02:20:36 +04:00
break ;
case CPUFREQ_POLICY_NOTIFIER :
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
ret = blocking_notifier_chain_register (
& cpufreq_policy_notifier_list , nb ) ;
2005-04-17 02:20:36 +04:00
break ;
default :
ret = - EINVAL ;
}
return ret ;
}
EXPORT_SYMBOL ( cpufreq_register_notifier ) ;
/**
* cpufreq_unregister_notifier - unregister a driver with cpufreq
* @ nb : notifier block to be unregistered
* @ list : CPUFREQ_TRANSITION_NOTIFIER or CPUFREQ_POLICY_NOTIFIER
*
* Remove a driver from the CPU frequency notifier list .
*
* This function may sleep , and has the same return conditions as
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
* blocking_notifier_chain_unregister .
2005-04-17 02:20:36 +04:00
*/
int cpufreq_unregister_notifier ( struct notifier_block * nb , unsigned int list )
{
int ret ;
2013-01-17 20:22:21 +04:00
if ( cpufreq_disabled ( ) )
return - EINVAL ;
2005-04-17 02:20:36 +04:00
switch ( list ) {
case CPUFREQ_TRANSITION_NOTIFIER :
2006-10-04 13:17:06 +04:00
ret = srcu_notifier_chain_unregister (
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
& cpufreq_transition_notifier_list , nb ) ;
2005-04-17 02:20:36 +04:00
break ;
case CPUFREQ_POLICY_NOTIFIER :
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
ret = blocking_notifier_chain_unregister (
& cpufreq_policy_notifier_list , nb ) ;
2005-04-17 02:20:36 +04:00
break ;
default :
ret = - EINVAL ;
}
return ret ;
}
EXPORT_SYMBOL ( cpufreq_unregister_notifier ) ;
/*********************************************************************
* GOVERNORS *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
int __cpufreq_driver_target ( struct cpufreq_policy * policy ,
unsigned int target_freq ,
unsigned int relation )
{
int retval = - EINVAL ;
2012-10-31 04:28:21 +04:00
unsigned int old_target_freq = target_freq ;
2005-10-31 01:59:54 +03:00
2012-03-14 03:18:39 +04:00
if ( cpufreq_disabled ( ) )
return - ENODEV ;
2012-10-31 04:28:21 +04:00
/* Make sure that target_freq is within supported range */
if ( target_freq > policy - > max )
target_freq = policy - > max ;
if ( target_freq < policy - > min )
target_freq = policy - > min ;
pr_debug ( " target for CPU %u: %u kHz, relation %u, requested %u kHz \n " ,
policy - > cpu , target_freq , relation , old_target_freq ) ;
2012-10-31 04:28:15 +04:00
if ( target_freq = = policy - > cur )
return 0 ;
2013-02-04 15:38:51 +04:00
if ( cpufreq_driver - > target )
2005-04-17 02:20:36 +04:00
retval = cpufreq_driver - > target ( policy , target_freq , relation ) ;
2005-11-09 08:34:24 +03:00
2005-04-17 02:20:36 +04:00
return retval ;
}
EXPORT_SYMBOL_GPL ( __cpufreq_driver_target ) ;
int cpufreq_driver_target ( struct cpufreq_policy * policy ,
unsigned int target_freq ,
unsigned int relation )
{
2008-07-26 00:44:53 +04:00
int ret = - EINVAL ;
2005-04-17 02:20:36 +04:00
policy = cpufreq_cpu_get ( policy - > cpu ) ;
if ( ! policy )
2008-07-26 00:44:53 +04:00
goto no_policy ;
2005-04-17 02:20:36 +04:00
2007-02-06 03:12:44 +03:00
if ( unlikely ( lock_policy_rwsem_write ( policy - > cpu ) ) )
2008-07-26 00:44:53 +04:00
goto fail ;
2005-04-17 02:20:36 +04:00
ret = __cpufreq_driver_target ( policy , target_freq , relation ) ;
2007-02-06 03:12:44 +03:00
unlock_policy_rwsem_write ( policy - > cpu ) ;
2005-04-17 02:20:36 +04:00
2008-07-26 00:44:53 +04:00
fail :
2005-04-17 02:20:36 +04:00
cpufreq_cpu_put ( policy ) ;
2008-07-26 00:44:53 +04:00
no_policy :
2005-04-17 02:20:36 +04:00
return ret ;
}
EXPORT_SYMBOL_GPL ( cpufreq_driver_target ) ;
2008-08-04 22:59:07 +04:00
int __cpufreq_driver_getavg ( struct cpufreq_policy * policy , unsigned int cpu )
2006-10-03 23:38:45 +04:00
{
int ret = 0 ;
2013-01-17 20:22:21 +04:00
if ( cpufreq_disabled ( ) )
return ret ;
2013-02-04 15:38:51 +04:00
if ( ! cpufreq_driver - > getavg )
2012-10-25 01:39:48 +04:00
return 0 ;
2006-10-03 23:38:45 +04:00
policy = cpufreq_cpu_get ( policy - > cpu ) ;
if ( ! policy )
return - EINVAL ;
2012-10-25 01:39:48 +04:00
ret = cpufreq_driver - > getavg ( policy , cpu ) ;
2006-10-03 23:38:45 +04:00
cpufreq_cpu_put ( policy ) ;
return ret ;
}
2007-02-06 03:12:44 +03:00
EXPORT_SYMBOL_GPL ( __cpufreq_driver_getavg ) ;
2006-10-03 23:38:45 +04:00
2006-07-26 17:40:07 +04:00
/*
* when " event " is CPUFREQ_GOV_LIMITS
*/
2005-04-17 02:20:36 +04:00
2006-10-26 14:50:58 +04:00
static int __cpufreq_governor ( struct cpufreq_policy * policy ,
unsigned int event )
2005-04-17 02:20:36 +04:00
{
2005-07-28 20:43:56 +04:00
int ret ;
2007-10-03 00:28:13 +04:00
/* Only must be defined when default governor is known to have latency
restrictions , like e . g . conservative or ondemand .
That this is the case is already ensured in Kconfig
*/
# ifdef CONFIG_CPU_FREQ_GOV_PERFORMANCE
struct cpufreq_governor * gov = & cpufreq_gov_performance ;
# else
struct cpufreq_governor * gov = NULL ;
# endif
2007-10-03 00:28:12 +04:00
if ( policy - > governor - > max_transition_latency & &
policy - > cpuinfo . transition_latency >
policy - > governor - > max_transition_latency ) {
2007-10-03 00:28:13 +04:00
if ( ! gov )
return - EINVAL ;
else {
printk ( KERN_WARNING " %s governor failed, too long "
" transition latency of HW, fallback "
" to %s governor \n " ,
policy - > governor - > name ,
gov - > name ) ;
policy - > governor = gov ;
}
2007-10-03 00:28:12 +04:00
}
2005-04-17 02:20:36 +04:00
if ( ! try_module_get ( policy - > governor - > owner ) )
return - EINVAL ;
2011-03-27 17:04:46 +04:00
pr_debug ( " __cpufreq_governor for CPU %u, event %u \n " ,
2006-10-26 14:50:58 +04:00
policy - > cpu , event ) ;
2005-04-17 02:20:36 +04:00
ret = policy - > governor - > governor ( policy , event ) ;
2013-03-27 19:58:58 +04:00
if ( ! ret ) {
if ( event = = CPUFREQ_GOV_POLICY_INIT )
policy - > governor - > initialized + + ;
else if ( event = = CPUFREQ_GOV_POLICY_EXIT )
policy - > governor - > initialized - - ;
}
2013-02-01 09:42:58 +04:00
2006-10-26 14:50:58 +04:00
/* we keep one module reference alive for
each CPU governed by this CPU */
2005-04-17 02:20:36 +04:00
if ( ( event ! = CPUFREQ_GOV_START ) | | ret )
module_put ( policy - > governor - > owner ) ;
if ( ( event = = CPUFREQ_GOV_STOP ) & & ! ret )
module_put ( policy - > governor - > owner ) ;
return ret ;
}
int cpufreq_register_governor ( struct cpufreq_governor * governor )
{
2006-07-06 23:30:26 +04:00
int err ;
2005-04-17 02:20:36 +04:00
if ( ! governor )
return - EINVAL ;
2012-03-14 03:18:39 +04:00
if ( cpufreq_disabled ( ) )
return - ENODEV ;
2006-01-14 02:54:22 +03:00
mutex_lock ( & cpufreq_governor_mutex ) ;
2006-02-28 08:43:23 +03:00
2013-02-01 09:42:58 +04:00
governor - > initialized = 0 ;
2006-07-06 23:30:26 +04:00
err = - EBUSY ;
if ( __find_governor ( governor - > name ) = = NULL ) {
err = 0 ;
list_add ( & governor - > governor_list , & cpufreq_governor_list ) ;
2005-04-17 02:20:36 +04:00
}
2006-02-28 08:43:23 +03:00
mutex_unlock ( & cpufreq_governor_mutex ) ;
2006-07-06 23:30:26 +04:00
return err ;
2005-04-17 02:20:36 +04:00
}
EXPORT_SYMBOL_GPL ( cpufreq_register_governor ) ;
void cpufreq_unregister_governor ( struct cpufreq_governor * governor )
{
2009-11-12 17:18:46 +03:00
# ifdef CONFIG_HOTPLUG_CPU
int cpu ;
# endif
2005-04-17 02:20:36 +04:00
if ( ! governor )
return ;
2012-03-14 03:18:39 +04:00
if ( cpufreq_disabled ( ) )
return ;
2009-11-12 17:18:46 +03:00
# ifdef CONFIG_HOTPLUG_CPU
for_each_present_cpu ( cpu ) {
if ( cpu_online ( cpu ) )
continue ;
if ( ! strcmp ( per_cpu ( cpufreq_cpu_governor , cpu ) , governor - > name ) )
strcpy ( per_cpu ( cpufreq_cpu_governor , cpu ) , " \0 " ) ;
}
# endif
2006-01-14 02:54:22 +03:00
mutex_lock ( & cpufreq_governor_mutex ) ;
2005-04-17 02:20:36 +04:00
list_del ( & governor - > governor_list ) ;
2006-01-14 02:54:22 +03:00
mutex_unlock ( & cpufreq_governor_mutex ) ;
2005-04-17 02:20:36 +04:00
return ;
}
EXPORT_SYMBOL_GPL ( cpufreq_unregister_governor ) ;
/*********************************************************************
* POLICY INTERFACE *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/**
* cpufreq_get_policy - get the current cpufreq_policy
2009-01-18 09:37:11 +03:00
* @ policy : struct cpufreq_policy into which the current cpufreq_policy
* is written
2005-04-17 02:20:36 +04:00
*
* Reads the current cpufreq policy .
*/
int cpufreq_get_policy ( struct cpufreq_policy * policy , unsigned int cpu )
{
struct cpufreq_policy * cpu_policy ;
if ( ! policy )
return - EINVAL ;
cpu_policy = cpufreq_cpu_get ( cpu ) ;
if ( ! cpu_policy )
return - EINVAL ;
memcpy ( policy , cpu_policy , sizeof ( struct cpufreq_policy ) ) ;
cpufreq_cpu_put ( cpu_policy ) ;
return 0 ;
}
EXPORT_SYMBOL ( cpufreq_get_policy ) ;
2006-07-26 17:40:07 +04:00
/*
2006-10-26 14:50:58 +04:00
* data : current policy .
* policy : policy to be set .
2006-07-26 17:40:07 +04:00
*/
2006-10-26 14:50:58 +04:00
static int __cpufreq_set_policy ( struct cpufreq_policy * data ,
struct cpufreq_policy * policy )
2005-04-17 02:20:36 +04:00
{
2013-03-27 19:58:57 +04:00
int ret = 0 , failed = 1 ;
2005-04-17 02:20:36 +04:00
2011-03-27 17:04:46 +04:00
pr_debug ( " setting new policy for CPU %u: %u - %u kHz \n " , policy - > cpu ,
2005-04-17 02:20:36 +04:00
policy - > min , policy - > max ) ;
2006-10-26 14:50:58 +04:00
memcpy ( & policy - > cpuinfo , & data - > cpuinfo ,
sizeof ( struct cpufreq_cpuinfo ) ) ;
2005-04-17 02:20:36 +04:00
2008-01-30 15:33:34 +03:00
if ( policy - > min > data - > max | | policy - > max < data - > min ) {
2006-07-06 01:12:20 +04:00
ret = - EINVAL ;
goto error_out ;
}
2005-04-17 02:20:36 +04:00
/* verify the cpu speed can be set within this limit */
ret = cpufreq_driver - > verify ( policy ) ;
if ( ret )
goto error_out ;
/* adjust if necessary - all reasons */
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
blocking_notifier_call_chain ( & cpufreq_policy_notifier_list ,
CPUFREQ_ADJUST , policy ) ;
2005-04-17 02:20:36 +04:00
/* adjust if necessary - hardware incompatibility*/
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
blocking_notifier_call_chain ( & cpufreq_policy_notifier_list ,
CPUFREQ_INCOMPATIBLE , policy ) ;
2005-04-17 02:20:36 +04:00
/* verify the cpu speed can be set within this limit,
which might be different to the first one */
ret = cpufreq_driver - > verify ( policy ) ;
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
if ( ret )
2005-04-17 02:20:36 +04:00
goto error_out ;
/* notification of the new policy */
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
blocking_notifier_call_chain ( & cpufreq_policy_notifier_list ,
CPUFREQ_NOTIFY , policy ) ;
2005-04-17 02:20:36 +04:00
2006-02-03 01:03:42 +03:00
data - > min = policy - > min ;
data - > max = policy - > max ;
2005-04-17 02:20:36 +04:00
2011-03-27 17:04:46 +04:00
pr_debug ( " new min and max freqs are %u - %u kHz \n " ,
2006-10-26 14:50:58 +04:00
data - > min , data - > max ) ;
2005-04-17 02:20:36 +04:00
if ( cpufreq_driver - > setpolicy ) {
data - > policy = policy - > policy ;
2011-03-27 17:04:46 +04:00
pr_debug ( " setting range \n " ) ;
2005-04-17 02:20:36 +04:00
ret = cpufreq_driver - > setpolicy ( policy ) ;
} else {
if ( policy - > governor ! = data - > governor ) {
/* save old, working values */
struct cpufreq_governor * old_gov = data - > governor ;
2011-03-27 17:04:46 +04:00
pr_debug ( " governor switch \n " ) ;
2005-04-17 02:20:36 +04:00
/* end old governor */
2013-03-27 19:58:57 +04:00
if ( data - > governor ) {
2005-04-17 02:20:36 +04:00
__cpufreq_governor ( data , CPUFREQ_GOV_STOP ) ;
2013-03-27 19:58:57 +04:00
__cpufreq_governor ( data ,
CPUFREQ_GOV_POLICY_EXIT ) ;
}
2005-04-17 02:20:36 +04:00
/* start new governor */
data - > governor = policy - > governor ;
2013-03-27 19:58:57 +04:00
if ( ! __cpufreq_governor ( data , CPUFREQ_GOV_POLICY_INIT ) ) {
if ( ! __cpufreq_governor ( data , CPUFREQ_GOV_START ) )
failed = 0 ;
else
__cpufreq_governor ( data ,
CPUFREQ_GOV_POLICY_EXIT ) ;
}
if ( failed ) {
2005-04-17 02:20:36 +04:00
/* new governor failed, so re-start old one */
2011-03-27 17:04:46 +04:00
pr_debug ( " starting governor %s failed \n " ,
2006-10-26 14:50:58 +04:00
data - > governor - > name ) ;
2005-04-17 02:20:36 +04:00
if ( old_gov ) {
data - > governor = old_gov ;
2013-03-27 19:58:57 +04:00
__cpufreq_governor ( data ,
CPUFREQ_GOV_POLICY_INIT ) ;
2006-10-26 14:50:58 +04:00
__cpufreq_governor ( data ,
CPUFREQ_GOV_START ) ;
2005-04-17 02:20:36 +04:00
}
ret = - EINVAL ;
goto error_out ;
}
/* might be a policy change, too, so fall through */
}
2011-03-27 17:04:46 +04:00
pr_debug ( " governor: change or update limits \n " ) ;
2005-04-17 02:20:36 +04:00
__cpufreq_governor ( data , CPUFREQ_GOV_LIMITS ) ;
}
2006-02-03 01:03:42 +03:00
error_out :
2005-04-17 02:20:36 +04:00
return ret ;
}
/**
* cpufreq_update_policy - re - evaluate an existing cpufreq policy
* @ cpu : CPU which shall be re - evaluated
*
2011-03-31 05:57:33 +04:00
* Useful for policy notifiers which have different necessities
2005-04-17 02:20:36 +04:00
* at different times .
*/
int cpufreq_update_policy ( unsigned int cpu )
{
struct cpufreq_policy * data = cpufreq_cpu_get ( cpu ) ;
struct cpufreq_policy policy ;
2008-07-26 00:44:53 +04:00
int ret ;
2005-04-17 02:20:36 +04:00
2008-07-26 00:44:53 +04:00
if ( ! data ) {
ret = - ENODEV ;
goto no_policy ;
}
2005-04-17 02:20:36 +04:00
2008-07-26 00:44:53 +04:00
if ( unlikely ( lock_policy_rwsem_write ( cpu ) ) ) {
ret = - EINVAL ;
goto fail ;
}
2005-04-17 02:20:36 +04:00
2011-03-27 17:04:46 +04:00
pr_debug ( " updating policy for CPU %u \n " , cpu ) ;
2006-02-03 01:03:42 +03:00
memcpy ( & policy , data , sizeof ( struct cpufreq_policy ) ) ;
2005-04-17 02:20:36 +04:00
policy . min = data - > user_policy . min ;
policy . max = data - > user_policy . max ;
policy . policy = data - > user_policy . policy ;
policy . governor = data - > user_policy . governor ;
2006-01-26 20:46:33 +03:00
/* BIOS might change freq behind our back
- > ask driver for current freq and notify governors about a change */
if ( cpufreq_driver - > get ) {
policy . cur = cpufreq_driver - > get ( cpu ) ;
2006-02-01 13:36:04 +03:00
if ( ! data - > cur ) {
2011-03-27 17:04:46 +04:00
pr_debug ( " Driver did not initialize current freq " ) ;
2006-02-01 13:36:04 +03:00
data - > cur = policy . cur ;
} else {
2013-02-06 21:02:09 +04:00
if ( data - > cur ! = policy . cur & & cpufreq_driver - > target )
2006-10-26 14:50:58 +04:00
cpufreq_out_of_sync ( cpu , data - > cur ,
policy . cur ) ;
2006-02-01 13:36:04 +03:00
}
2006-01-26 20:46:33 +03:00
}
2005-04-17 02:20:36 +04:00
ret = __cpufreq_set_policy ( data , & policy ) ;
2007-02-06 03:12:44 +03:00
unlock_policy_rwsem_write ( cpu ) ;
2008-07-26 00:44:53 +04:00
fail :
2005-04-17 02:20:36 +04:00
cpufreq_cpu_put ( data ) ;
2008-07-26 00:44:53 +04:00
no_policy :
2005-04-17 02:20:36 +04:00
return ret ;
}
EXPORT_SYMBOL ( cpufreq_update_policy ) ;
2007-10-03 00:28:14 +04:00
static int __cpuinit cpufreq_cpu_callback ( struct notifier_block * nfb ,
2005-10-31 01:59:54 +03:00
unsigned long action , void * hcpu )
{
unsigned int cpu = ( unsigned long ) hcpu ;
2011-12-22 02:29:42 +04:00
struct device * dev ;
2005-10-31 01:59:54 +03:00
2011-12-22 02:29:42 +04:00
dev = get_cpu_device ( cpu ) ;
if ( dev ) {
2005-10-31 01:59:54 +03:00
switch ( action ) {
case CPU_ONLINE :
2007-05-09 13:35:10 +04:00
case CPU_ONLINE_FROZEN :
2011-12-22 02:29:42 +04:00
cpufreq_add_dev ( dev , NULL ) ;
2005-10-31 01:59:54 +03:00
break ;
case CPU_DOWN_PREPARE :
2007-05-09 13:35:10 +04:00
case CPU_DOWN_PREPARE_FROZEN :
2011-12-22 02:29:42 +04:00
__cpufreq_remove_dev ( dev , NULL ) ;
2005-10-31 01:59:54 +03:00
break ;
2007-02-06 03:12:44 +03:00
case CPU_DOWN_FAILED :
2007-05-09 13:35:10 +04:00
case CPU_DOWN_FAILED_FROZEN :
2011-12-22 02:29:42 +04:00
cpufreq_add_dev ( dev , NULL ) ;
2005-10-31 01:59:54 +03:00
break ;
}
}
return NOTIFY_OK ;
}
2010-06-23 07:02:44 +04:00
static struct notifier_block __refdata cpufreq_cpu_notifier = {
2005-10-31 01:59:54 +03:00
. notifier_call = cpufreq_cpu_callback ,
} ;
2005-04-17 02:20:36 +04:00
/*********************************************************************
* REGISTER / UNREGISTER CPUFREQ DRIVER *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/**
* cpufreq_register_driver - register a CPU Frequency driver
* @ driver_data : A struct cpufreq_driver containing the values #
* submitted by the CPU Frequency driver .
*
2006-02-28 08:43:23 +03:00
* Registers a CPU Frequency driver to this core code . This code
2005-04-17 02:20:36 +04:00
* returns zero on success , - EBUSY when another driver got here first
2006-02-28 08:43:23 +03:00
* ( and isn ' t unregistered in the meantime ) .
2005-04-17 02:20:36 +04:00
*
*/
2007-02-27 01:55:48 +03:00
int cpufreq_register_driver ( struct cpufreq_driver * driver_data )
2005-04-17 02:20:36 +04:00
{
unsigned long flags ;
int ret ;
2012-03-14 03:18:39 +04:00
if ( cpufreq_disabled ( ) )
return - ENODEV ;
2005-04-17 02:20:36 +04:00
if ( ! driver_data | | ! driver_data - > verify | | ! driver_data - > init | |
( ( ! driver_data - > setpolicy ) & & ( ! driver_data - > target ) ) )
return - EINVAL ;
2011-03-27 17:04:46 +04:00
pr_debug ( " trying to register driver %s \n " , driver_data - > name ) ;
2005-04-17 02:20:36 +04:00
if ( driver_data - > setpolicy )
driver_data - > flags | = CPUFREQ_CONST_LOOPS ;
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
if ( cpufreq_driver ) {
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
return - EBUSY ;
}
cpufreq_driver = driver_data ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
2011-12-22 02:29:42 +04:00
ret = subsys_interface_register ( & cpufreq_interface ) ;
2011-03-01 19:41:10 +03:00
if ( ret )
goto err_null_driver ;
2005-04-17 02:20:36 +04:00
2011-03-01 19:41:10 +03:00
if ( ! ( cpufreq_driver - > flags & CPUFREQ_STICKY ) ) {
2005-04-17 02:20:36 +04:00
int i ;
ret = - ENODEV ;
/* check for at least one working CPU */
2008-03-26 01:06:53 +03:00
for ( i = 0 ; i < nr_cpu_ids ; i + + )
if ( cpu_possible ( i ) & & per_cpu ( cpufreq_cpu_data , i ) ) {
2005-04-17 02:20:36 +04:00
ret = 0 ;
2008-03-26 01:06:53 +03:00
break ;
}
2005-04-17 02:20:36 +04:00
/* if all ->init() calls failed, unregister */
if ( ret ) {
2011-03-27 17:04:46 +04:00
pr_debug ( " no CPU initialized for driver %s \n " ,
2006-10-26 14:50:58 +04:00
driver_data - > name ) ;
2011-12-22 02:29:42 +04:00
goto err_if_unreg ;
2005-04-17 02:20:36 +04:00
}
}
2011-03-01 19:41:10 +03:00
register_hotcpu_notifier ( & cpufreq_cpu_notifier ) ;
2011-03-27 17:04:46 +04:00
pr_debug ( " driver %s up and running \n " , driver_data - > name ) ;
2005-04-17 02:20:36 +04:00
2011-03-01 19:41:10 +03:00
return 0 ;
2011-12-22 02:29:42 +04:00
err_if_unreg :
subsys_interface_unregister ( & cpufreq_interface ) ;
2011-03-01 19:41:10 +03:00
err_null_driver :
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2011-03-01 19:41:10 +03:00
cpufreq_driver = NULL ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2008-02-08 00:33:49 +03:00
return ret ;
2005-04-17 02:20:36 +04:00
}
EXPORT_SYMBOL_GPL ( cpufreq_register_driver ) ;
/**
* cpufreq_unregister_driver - unregister the current CPUFreq driver
*
2006-02-28 08:43:23 +03:00
* Unregister the current CPUFreq driver . Only call this if you have
2005-04-17 02:20:36 +04:00
* the right to do so , i . e . if you have succeeded in initialising before !
* Returns zero if successful , and - EINVAL if the cpufreq_driver is
* currently not initialised .
*/
2007-02-27 01:55:48 +03:00
int cpufreq_unregister_driver ( struct cpufreq_driver * driver )
2005-04-17 02:20:36 +04:00
{
unsigned long flags ;
2011-03-27 17:04:46 +04:00
if ( ! cpufreq_driver | | ( driver ! = cpufreq_driver ) )
2005-04-17 02:20:36 +04:00
return - EINVAL ;
2011-03-27 17:04:46 +04:00
pr_debug ( " unregistering driver %s \n " , driver - > name ) ;
2005-04-17 02:20:36 +04:00
2011-12-22 02:29:42 +04:00
subsys_interface_unregister ( & cpufreq_interface ) ;
2006-06-27 13:54:08 +04:00
unregister_hotcpu_notifier ( & cpufreq_cpu_notifier ) ;
2005-04-17 02:20:36 +04:00
2013-02-22 20:24:34 +04:00
write_lock_irqsave ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
cpufreq_driver = NULL ;
2013-02-22 20:24:34 +04:00
write_unlock_irqrestore ( & cpufreq_driver_lock , flags ) ;
2005-04-17 02:20:36 +04:00
return 0 ;
}
EXPORT_SYMBOL_GPL ( cpufreq_unregister_driver ) ;
2007-02-06 03:12:44 +03:00
static int __init cpufreq_core_init ( void )
{
int cpu ;
2012-03-14 03:18:39 +04:00
if ( cpufreq_disabled ( ) )
return - ENODEV ;
2007-02-06 03:12:44 +03:00
for_each_possible_cpu ( cpu ) {
2009-10-29 16:34:13 +03:00
per_cpu ( cpufreq_policy_cpu , cpu ) = - 1 ;
2007-02-06 03:12:44 +03:00
init_rwsem ( & per_cpu ( cpu_policy_rwsem , cpu ) ) ;
}
2009-07-24 17:25:05 +04:00
2011-12-22 02:29:42 +04:00
cpufreq_global_kobject = kobject_create_and_add ( " cpufreq " , & cpu_subsys . dev_root - > kobj ) ;
2009-07-24 17:25:05 +04:00
BUG_ON ( ! cpufreq_global_kobject ) ;
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-03-24 00:16:32 +03:00
register_syscore_ops ( & cpufreq_syscore_ops ) ;
2009-07-24 17:25:05 +04:00
2007-02-06 03:12:44 +03:00
return 0 ;
}
core_initcall ( cpufreq_core_init ) ;