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 v4 0/5] CPU unplug timeout/LMB unplug cleanup in DRC reconfiguration
Date: Mon, 22 Feb 2021 16:45:26 -0300 [thread overview]
Message-ID: <20210222194531.62717-1-danielhb413@gmail.com> (raw)
Hi,
This new version contains fixes proposed during the review of v3.
Patches were rebased on top of David's ppc-for-6.0.
changes from v3:
- former patch 1: already pushed to ppc-for-6.0
- former patch 2: dropped
- all patches: commit message trimmed to < 76 chars per line
- all patches: added R-bs from previous review
- patch 3:
* removed the migratable state of the unplug timer
* added a 'spapr_drc_start_unplug_timeout_timer()' helper to start the timer
* added a .post_load implementation to vmstate_spapr_drc, pointed to
a new spapr_drc_post_load() function
* spapr_drc_post_load() starts the DRC unplug timer from the beginning using
spapr_drc_start_unplug_timeout_timer()
- patch 4:
* use spapr_drc_start_unplug_timeout_timer() to start the timer in spapr_drc_unplug_request()
(To David: I kept your Reviewed-by in this patch despite this change - feel free
to review it again)
- patch 5:
* removed the 'DIMM' wording when referring to kernel internals
* move the g_assert() to spapr_clear_pending_dimm_unplug_state()
* do not g_assert(dev), but g_assert(ds) if dev != NULL inside
spapr_clear_pending_dimm_unplug_state()
- v3 link: https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg04196.html
Daniel Henrique Barboza (5):
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 | 53 ++++++++++++++++++--
hw/ppc/spapr_drc.c | 99 +++++++++++++++++++++++++++++++-------
hw/ppc/spapr_pci.c | 4 +-
hw/ppc/trace-events | 2 +-
include/hw/ppc/spapr.h | 2 +
include/hw/ppc/spapr_drc.h | 7 ++-
6 files changed, 142 insertions(+), 25 deletions(-)
--
2.29.2
next reply other threads:[~2021-02-22 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:45 Daniel Henrique Barboza [this message]
2021-02-22 19:45 ` [PATCH v4 1/5] spapr_drc.c: use spapr_drc_release() in isolate_physical/set_unusable Daniel Henrique Barboza
2021-02-23 0:12 ` David Gibson
2021-02-22 19:45 ` [PATCH v4 2/5] spapr: rename spapr_drc_detach() to spapr_drc_unplug_request() Daniel Henrique Barboza
2021-02-23 0:13 ` David Gibson
2021-02-22 19:45 ` [PATCH v4 3/5] spapr_drc.c: introduce unplug_timeout_timer Daniel Henrique Barboza
2021-02-22 19:45 ` [PATCH v4 4/5] spapr_drc.c: add hotunplug timeout for CPUs Daniel Henrique Barboza
2021-02-22 19:45 ` [PATCH v4 5/5] spapr_drc.c: use DRC reconfiguration to cleanup DIMM unplug state Daniel Henrique Barboza
2021-02-23 4:31 ` [PATCH v4 0/5] 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=20210222194531.62717-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).