From: Nathan Lynch <nathanl@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/3] more migration vs CPU hotplug fixes etc
Date: Fri, 2 Aug 2019 14:29:23 -0500 [thread overview]
Message-ID: <20190802192926.19277-1-nathanl@linux.ibm.com> (raw)
Despite recent fixes, userspace-initiated CPU hotplug still can
destructively race with the migration code's CPU state
manipulations. And parts of the LPM implementation have potentially
long-running code, especially on larger systems, that ties up the CPU
causing RCU stalls etc.
Changes since v1:
- Correct description of cpu hotplug vs LPM race.
- Add fix for long-running code in pseries_devicetree_update and friends
Nathan Lynch (3):
powerpc/rtas: use device model APIs and serialization during LPM
powerpc/rtas: allow rescheduling while changing cpu states
powerpc/pseries/mobility: use cond_resched when updating device tree
arch/powerpc/kernel/rtas.c | 13 ++++++++++---
arch/powerpc/platforms/pseries/mobility.c | 9 +++++++++
2 files changed, 19 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2019-08-02 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 19:29 Nathan Lynch [this message]
2019-08-02 19:29 ` [PATCH v2 1/3] powerpc/rtas: use device model APIs and serialization during LPM Nathan Lynch
2019-08-05 23:05 ` Tyrel Datwyler
2019-08-12 16:55 ` Nathan Lynch
2019-08-13 17:20 ` Gautham R Shenoy
2019-08-22 13:08 ` Michael Ellerman
2019-08-02 19:29 ` [PATCH v2 2/3] powerpc/rtas: allow rescheduling while changing cpu states Nathan Lynch
2019-08-13 17:17 ` Gautham R Shenoy
2019-08-13 18:14 ` Nathan Lynch
2019-08-02 19:29 ` [PATCH v2 3/3] powerpc/pseries/mobility: use cond_resched when updating device tree Nathan Lynch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190802192926.19277-1-nathanl@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).