Thread (12 messages) flat view 12 messages, 3 authors, 2016-06-14
STALE3738d

[PATCH 3/5] PM / Hibernate: Allow architectures to specify the hibernate/resume CPU

From: Rafael J. Wysocki <hidden>
Date: 2016-06-13 22:05:28
Also in: linux-pm

On Thursday, June 02, 2016 03:10:55 PM James Morse wrote:
On arm64 the cpu with logical id 0 is assumed to be the boot CPU. If a
user hotplugs this CPU out, then uses kexec to boot a new kernel, the new
kernel will assign logical id 0 to a different physical CPU.
This breaks hibernate as hibernate and resume will be attempted on different
CPUs.

Define a weak symbol arch_hibernation_disable_cpus(), which defaults to
calling disable_nonboot_cpus). Architectures that allow CPU 0 to be
hotplugged can use this to control which CPU is used for hibernate/resume.

Signed-off-by: James Morse <james.morse@arm.com>
Cc: Rafael J. Wysocki <redacted>
Cc: Pavel Machek <redacted>
---
I would have preferred a macro, but there is no hibernate-relevant header
file that all arch's have. arm, arm64 and x86 have a suspend.h, but powerpc
doesn't.
What about include/linux/suspend.h?

There are arch_ things declared in there.

Thanks,
Rafael
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help