diff options
| author |   Sam Bobroff <sam.bobroff@au1.ibm.com> | 2018-02-12 11:19:29 +1100 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2018-02-13 22:37:46 +1100 |
| commit | c9dccf1d074a67d36c510845f663980d69e3409b (patch) | |
| tree | 9ecce5e6372c85b275f35d77c296a4f668c5774e /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | powerpc/mm/radix: Split linear mapping on hot-unplug (diff) | |
| download | wireguard-linux-c9dccf1d074a67d36c510845f663980d69e3409b.tar.xz wireguard-linux-c9dccf1d074a67d36c510845f663980d69e3409b.zip | |
powerpc/pseries: Enable RAS hotplug events later
Currently if the kernel receives a memory hot-unplug event early
enough, it may get stuck in an infinite loop in
dissolve_free_huge_pages(). This appears as a stall just after:
pseries-hotplug-mem: Attempting to hot-remove XX LMB(s) at YYYYYYYY
It appears to be caused by "minimum_order" being uninitialized, due to
init_ras_IRQ() executing before hugetlb_init().
To correct this, extract the part of init_ras_IRQ() that enables
hotplug event processing and place it in the machine_late_initcall
phase, which is guaranteed to be after hugetlb_init() is called.
Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
Acked-by: Balbir Singh <bsingharora@gmail.com>
[mpe: Reorder the functions to make the diff readable]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions