summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorJames Morse <james.morse@arm.com>2020-05-01 17:45:41 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2020-05-19 19:51:10 +0200
commit062022315e8ad9e0628515dfc756ab54b5fdb26b (patch)
treead804a60ffac8836c902c50e815f4d51468ebaed /block
parentb9bbe6ed63b2b9f2c9ee5cbd0f2c946a2723f4ce (diff)
downloadlinux-stable-062022315e8ad9e0628515dfc756ab54b5fdb26b.tar.gz
linux-stable-062022315e8ad9e0628515dfc756ab54b5fdb26b.tar.bz2
linux-stable-062022315e8ad9e0628515dfc756ab54b5fdb26b.zip
mm/memory-failure: Add memory_failure_queue_kick()
The GHES code calls memory_failure_queue() from IRQ context to schedule work on the current CPU so that memory_failure() can sleep. For synchronous memory errors the arch code needs to know any signals that memory_failure() will trigger are pending before it returns to user-space, possibly when exiting from the IRQ. Add a helper to kick the memory failure queue, to ensure the scheduled work has happened. This has to be called from process context, so may have been migrated from the original cpu. Pass the cpu the work was queued on. Change memory_failure_work_func() to permit being called on the 'wrong' cpu. Signed-off-by: James Morse <james.morse@arm.com> Tested-by: Tyler Baicar <baicar@os.amperecomputing.com> Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions