summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoerg Roedel <jroedel@suse.de>2014-07-21 12:27:02 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2014-07-29 01:47:44 +0200
commit0f7d83e85dbd5bb8032ebed7713edf59670fb074 (patch)
tree9db80e148252ef099ed944878cfa758fbdf8c203
parentPM / Hibernate: Remove the old memory-bitmap implementation (diff)
downloadlinux-0f7d83e85dbd5bb8032ebed7713edf59670fb074.tar.xz
linux-0f7d83e85dbd5bb8032ebed7713edf59670fb074.zip
PM / Hibernate: Touch Soft Lockup Watchdog in rtree_next_node
When a memory bitmap is fully populated on a large memory machine (several TB of RAM) it can take more than a minute to walk through all bits. This causes the soft lockup detector on these machine to report warnings. Avoid this by touching the soft lockup watchdog in the memory bitmap walking code. Signed-off-by: Joerg Roedel <jroedel@suse.de> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
-rw-r--r--kernel/power/snapshot.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/kernel/power/snapshot.c b/kernel/power/snapshot.c
index ab1998adb0a9..4fc5c32422b3 100644
--- a/kernel/power/snapshot.c
+++ b/kernel/power/snapshot.c
@@ -769,6 +769,7 @@ static bool rtree_next_node(struct memory_bitmap *bm)
if (&bm->cur.node->list != &bm->cur.zone->leaves) {
bm->cur.node_pfn += BM_BITS_PER_BLOCK;
bm->cur.node_bit = 0;
+ touch_softlockup_watchdog();
return true;
}