This document gives a brief rationale for the TINY_RCU test cases. Kconfig Parameters: CONFIG_DEBUG_LOCK_ALLOC -- Do all three and none of the three. CONFIG_PREEMPT_COUNT CONFIG_RCU_TRACE The theory here is that randconfig testing will hit the other six possible combinations of these parameters. Kconfig Parameters Ignored: CONFIG_DEBUG_OBJECTS_RCU_HEAD CONFIG_PROVE_RCU In common code tested by TREE_RCU test cases. CONFIG_NO_HZ_FULL_SYSIDLE CONFIG_RCU_NOCB_CPU Meaningless for TINY_RCU. CONFIG_RCU_STALL_COMMON CONFIG_RCU_TORTURE_TEST Redundant with CONFIG_RCU_TRACE. CONFIG_HOTPLUG_CPU CONFIG_PREEMPT CONFIG_PREEMPT_RCU CONFIG_SMP CONFIG_TINY_RCU CONFIG_PREEMPT_RCU CONFIG_TREE_RCU All forced by CONFIG_TINY_RCU. 'cgit logo'/> index : net-next.git
net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/net/xfrm/xfrm_policy.c
diff options
context:
space:
mode:
authorMarkus Mayer <mmayer@broadcom.com>2016-12-19 12:10:28 -0800
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-01-27 11:43:49 +0100
commit3c223c19aea85d3dda1416c187915f4a30b04b1f (patch)
tree2d2021f8161db3e9ed38b9a966a225b66dff8e58 /net/xfrm/xfrm_policy.c
parent9b02c54bc951fca884ba5719f42a27e8240965bf (diff)
cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend
The AVS GET_PMAP command does return a P-state along with the P-map information. However, that P-state is the initial P-state when the P-map was first downloaded to AVS. It is *not* the current P-state. Therefore, we explicitly retrieve the P-state using the GET_PSTATE command. Signed-off-by: Markus Mayer <mmayer@broadcom.com> Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'net/xfrm/xfrm_policy.c')