From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, groug@kaod.org, david@gibson.dropbear.id.au
Subject: [PATCH v3 0/7] CPU unplug timeout/LMB unplug cleanup in DRC reconfiguration
Date: Thu, 11 Feb 2021 19:52:39 -0300 [thread overview]
Message-ID: <20210211225246.17315-1-danielhb413@gmail.com> (raw)
Hi,
This is marked as a v3 as it started as a result of discussions that
followed the v2 [1].
The idea with this series is to add CPU hotunplug timeout to avoid the
situations where the kernel refuses to release the CPU. The reasoning
for a timeout approach is described in patch 05.
While investigating putting a timeout in memory hotunplug, I have found
out that we have a way to determine, at least in some cases, when the kernel
refuses to release the DIMM during a memory hotunplug. This alleviate one
of the most common issues (at least AFAIK) with memory hotunplug and it
made me gave up attempting to put a timeout in memory hotunplug altogether.
At this point I didn't add timeouts for PCI hotunplug operations, but it
is trivial to do so if desirable.
The series goes as follows:
- Patches 1-4: DRC simplifications/cleanups. The idea with these
cleanups were to trim the spapr_drc_detach use as much as possible,
since the function would be used to start the timeout timer
- Patch 5: timeout timer infrastructure
- Patch 6: add cpu unplug timeout
- Patch 7: reset DIMM unplug state when the kernel reconfigures the DRC
connector
v2 link: [1] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg04400.html
Daniel Henrique Barboza (7):
spapr_drc.c: do not call spapr_drc_detach() in drc_isolate_logical()
spapr_pci.c: simplify spapr_pci_unplug_request() function handling
spapr_drc.c: use spapr_drc_release() in isolate_physical/set_unusable
spapr: rename spapr_drc_detach() to spapr_drc_unplug_request()
spapr_drc.c: introduce unplug_timeout_timer
spapr_drc.c: add hotunplug timeout for CPUs
spapr_drc.c: use DRC reconfiguration to cleanup DIMM unplug state
hw/ppc/spapr.c | 40 ++++++++++++-
hw/ppc/spapr_drc.c | 116 +++++++++++++++++++++++++++----------
hw/ppc/spapr_pci.c | 44 +++++---------
hw/ppc/trace-events | 2 +-
include/hw/ppc/spapr.h | 2 +
include/hw/ppc/spapr_drc.h | 7 ++-
6 files changed, 147 insertions(+), 64 deletions(-)
--
2.29.2
next reply other threads:[~2021-02-11 22:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 22:52 Daniel Henrique Barboza [this message]
2021-02-11 22:52 ` [PATCH v3 1/7] spapr_drc.c: do not call spapr_drc_detach() in drc_isolate_logical() Daniel Henrique Barboza
2021-02-15 10:40 ` Greg Kurz
2021-02-17 0:51 ` David Gibson
2021-02-11 22:52 ` [PATCH v3 2/7] spapr_pci.c: simplify spapr_pci_unplug_request() function handling Daniel Henrique Barboza
2021-02-16 15:50 ` Greg Kurz
2021-02-16 16:09 ` Daniel Henrique Barboza
2021-02-16 17:16 ` Greg Kurz
2021-02-16 17:44 ` Daniel Henrique Barboza
2021-02-17 0:54 ` David Gibson
2021-02-11 22:52 ` [PATCH v3 3/7] spapr_drc.c: use spapr_drc_release() in isolate_physical/set_unusable Daniel Henrique Barboza
2021-02-17 0:57 ` David Gibson
2021-02-17 10:58 ` Greg Kurz
2021-02-11 22:52 ` [PATCH v3 4/7] spapr: rename spapr_drc_detach() to spapr_drc_unplug_request() Daniel Henrique Barboza
2021-02-17 0:58 ` David Gibson
2021-02-17 11:01 ` Greg Kurz
2021-02-11 22:52 ` [PATCH v3 5/7] spapr_drc.c: introduce unplug_timeout_timer Daniel Henrique Barboza
2021-02-17 1:14 ` David Gibson
2021-02-17 1:20 ` David Gibson
2021-02-11 22:52 ` [PATCH v3 6/7] spapr_drc.c: add hotunplug timeout for CPUs Daniel Henrique Barboza
2021-02-17 1:23 ` David Gibson
2021-02-11 22:52 ` [PATCH v3 7/7] spapr_drc.c: use DRC reconfiguration to cleanup DIMM unplug state Daniel Henrique Barboza
2021-02-17 2:31 ` David Gibson
2021-02-19 20:04 ` Daniel Henrique Barboza
2021-02-22 5:53 ` David Gibson
2021-02-19 21:31 ` Daniel Henrique Barboza
2021-02-22 5:54 ` David Gibson
2021-02-17 2:33 ` [PATCH v3 0/7] CPU unplug timeout/LMB unplug cleanup in DRC reconfiguration David Gibson
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=20210211225246.17315-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).