28 Apr, 2014
1 commit
-
Up until now we have been setting the runlatch bits for a busy CPU and
clearing it when a CPU enters idle state. The runlatch bit has thus
been consistent with the utilization of a CPU as long as the CPU is online.However when a CPU is hotplugged out the runlatch bit is not cleared. It
needs to be cleared to indicate an unused CPU. Hence this patch has the
runlatch bit cleared for an offline CPU just before entering an idle state
and sets it immediately after it exits the idle state.Signed-off-by: Preeti U Murthy
Acked-by: Paul Mackerras
Reviewed-by: Srivatsa S. Bhat
Signed-off-by: Benjamin Herrenschmidt
14 Aug, 2013
1 commit
-
T4, Cell, powernv, and pseries had the same implementation, so switch
them to use a generic version. A2 apparently had a version, but
removed it at some point, so we remove the declaration, too.Signed-off-by: Andy Fleming
Signed-off-by: Benjamin Herrenschmidt
01 Jul, 2013
1 commit
-
The __cpuinit type of throwaway sections might have made sense
some time ago when RAM was more constrained, but now the savings
do not offset the cost and complications. For example, the fix in
commit 5e427ec2d0 ("x86: Fix bit corruption at CPU resume time")
is a good example of the nasty type of bugs that can be created
with improper use of the various __init prefixes.After a discussion on LKML[1] it was decided that cpuinit should go
the way of devinit and be phased out. Once all the users are gone,
we can then finally remove the macros themselves from linux/init.h.This removes all the powerpc uses of the __cpuinit macros. There
are no __CPUINIT users in assembly files in powerpc.[1] https://lkml.org/lkml/2013/5/20/589
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Josh Boyer
Cc: Matt Porter
Cc: Kumar Gala
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Paul Gortmaker
Signed-off-by: Benjamin Herrenschmidt
20 Jun, 2013
1 commit
-
'system_state < SYSTEM_RUNNING' will have same effect
with 'system_state == SYSTEM_BOOTING', but the later
one is more clearer.Signed-off-by: liguang
Signed-off-by: Benjamin Herrenschmidt
14 May, 2013
1 commit
-
The current code fails to handle kexec on OPALv2. This fixes it
and adds code to improve the situation on OPALv3 where we can
query the CPU status from the firmware and decide what to do
based on that.Signed-off-by: Benjamin Herrenschmidt
06 May, 2013
1 commit
-
If OPAL returns an error, propagate it upward rather than spinning
seconds waiting for a CPU that will never show upSigned-off-by: Benjamin Herrenschmidt
Signed-off-by: Benjamin Herrenschmidt
04 Jan, 2013
1 commit
-
CONFIG_HOTPLUG is going away as an option. As a result, the __dev*
markings need to be removed.This change removes the use of __devinit, __devexit_p, __devinitdata,
__devinitconst, and __devexit from these drivers.Based on patches originally written by Bill Pemberton, but redone by me
in order to handle some of the coding style issues better, by hand.Cc: Bill Pemberton
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Signed-off-by: Greg Kroah-Hartman
05 Sep, 2012
1 commit
-
The CPU hotplug code for the powernv platform currently only puts
offline CPUs into nap mode if the powersave_nap variable is set.
However, HV-style KVM on this platform requires secondary CPU threads
to be offline and in nap mode. Since we know nap mode works just
fine on all POWER7 machines, and the only machines that support the
powernv platform are POWER7 machines, this changes the code to
always put offline CPUs into nap mode, regardless of powersave_nap.
Powersave_nap still controls whether or not CPUs go into nap mode
when idle, as before.Signed-off-by: Paul Mackerras
Signed-off-by: Benjamin Herrenschmidt
29 Mar, 2012
1 commit
-
Disintegrate asm/system.h for PowerPC.
Signed-off-by: David Howells
Acked-by: Benjamin Herrenschmidt
cc: linuxppc-dev@lists.ozlabs.org
08 Dec, 2011
1 commit
-
At present, on the powernv platform, if you off-line a CPU that was
online, and then try to on-line it again, the kernel generates a
warning message "OPAL Error -1 starting CPU n". Furthermore, if the
CPU is a secondary thread that was used by KVM while it was off-line,
the CPU fails to come online.The first problem is fixed by only calling OPAL to start the CPU the
first time it is on-lined, as indicated by the cpu_start field of its
PACA being zero. The second problem is fixed by restoring the
cpu_start field to 1 instead of 0 when using the CPU within KVM.Signed-off-by: Paul Mackerras
Signed-off-by: Benjamin Herrenschmidt
20 Sep, 2011
3 commits
-
Add definition of OPAL interfaces along with the wrappers to call
into OPAL runtime and the early device-tree parsing hook to locate
the OPAL runtime firmware.Signed-off-by: Benjamin Herrenschmidt
-
Unplugged CPU go into NAP mode in a loop until woken up
Signed-off-by: Benjamin Herrenschmidt
-
This adds a skeletton for the new Power "Non Virtualized"
platform which will be used by machines supporting running
without an hypervisor, for example in order to run KVM.These machines will be using a new firmware called OPAL
for which the support will be provided by later patches.The PowerNV platform is intended to be also usable under
the BML environment used internally for early CPU bringup
which is why the code also supports using RTAS instead of
OPAL in various places.Signed-off-by: Benjamin Herrenschmidt