From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au,
bharata@linux.vnet.ibm.com, nfont@linux.vnet.ibm.com,
jallen@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/6] spapr: dedicated hotplug events and memory unplug support
Date: Wed, 26 Oct 2016 21:20:24 -0500 [thread overview]
Message-ID: <1477534830-25495-1-git-send-email-mdroth@linux.vnet.ibm.com> (raw)
This series is based on David's ppc-for-2.8 branch, and is also available from:
https://github.com/mdroth/qemu/commits/spapr-hotplug-event-update
Changes since v2:
* Rebased on latest ppc-for-2.8
* Fix silly screw up with Reviewed-by attributions
Changes since v1:
* Rebased on latest ppc-for-2.8
* Dropped patches relating to option vector manipulation (now merged)
* Moved patch introducing modern-hotplug-events option to come after
that actual implementation of modern-hotplug-events support. (David)
* Removed uneeded source name string from sPAPREventSource in favor of
manual lookup of the name when creating DT. (David)
* Don't split function return signatures across lines (David)
* Add comment to clarify hotplug events being enabled regardless
of CAS-negotiation.
* Avoid unecessary initialization of hotplug_ctrl in
spapr_lmb_release. (David)
Changes since RFC:
* Rebased on latest ppc-for-2.8 (with DT refactoring)
* Submitting as v1 now that PAPR Hotplug ACR is committed
* address Patchew warnings
* add comments to clarify spapr->ov5/ov5_cas usage. (David)
* revise comment to clarify intent when setting spapr->ov5
OV5_HP_EVT bit. (Bharata)
* drop internal usage of spapr_ovec_from_bitmap() in favor of
directly assigning bitmap to sPAPROptionVector instances. (David)
* standardize meaning of 'vector_len' variable through spapr_ovec_*
functions to be the byte-wise length of option vectors entries,
and not including the preceeding length byte itself. (David)
* fix spapr_ovec_populate_dt() to parse up to OV_MAXBITS bits
rather than OV_MAXBITS - 1. (David)
* fix spapr_ovec_populate_dt() encode the minimum of 1 option
vector byte instead of the max of OV_MAXBYTES in cases where
no option bits are set. (David)
* add some comments to spapr_ovec_populate_dt() to clarify what
is being encoded into length byte of ibm,architecture-vec-5
* switch 'legacy-hotplug-events' option to
'modern-hotplug-events' (David)
* modify rtas_event_log_to_source() to check for OV5_HP_EVT
option rather than relying on whether the hotplug source is
specifically enabled. Assert the latter in cases where
OV5_HP_EVT is set. (Bharata)
* drop global EventSource list in favor of an sPAPREventSource
list field within sPAPRMachineState (David)
* add CPU unplug hook in mc->unplug_request (Bharata)
Patches 1-4 add support for an updated event format for hotplug events,
which includes a new way to specify a range of DRCs/LMBs to hotplug/unplug
using a starting position and count, which is necessary for memory unplug.
Patches 5-6 add support for memory unplug using the new event format.
In addition to kernel 4.8 or later, there are a number of patches required
to enable support on the guest kernel side. I've including the minimum set
of patches in my branch here:
https://github.com/mdroth/linux/commits/spapr-hotplug-event-update
*powerpc/pseries: advertise Hot Plug Event support to firmware
powerpc/pseries: Implement indexed-count hotplug memory remove
powerpc/pseries: Implement indexed-count hotplug memory add
Note that there is currently an issue that arises when attempting to
offline an LMB that was onlined using a guest kernel's auto-onlining
mechanism, which can prevent full completion of memory unplug requests.
This is being investigated, but for the purposes of testing this can
be worked around currently by disabling auto-onlining in guests via:
"echo offline >/sys/devices/system/memory/auto_online_blocks"
and instead onlining the blocks manually or via udev.
docs/specs/ppc-spapr-hotplug.txt | 55 +++++++++++++++++++++-----
hw/ppc/spapr.c | 178 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
hw/ppc/spapr_drc.c | 17 ++++++++
hw/ppc/spapr_events.c | 278 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------
include/hw/ppc/spapr.h | 10 ++++-
include/hw/ppc/spapr_ovec.h | 1 +
6 files changed, 469 insertions(+), 70 deletions(-)
next reply other threads:[~2016-10-27 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 2:20 Michael Roth [this message]
2016-10-27 2:20 ` [Qemu-devel] [PATCH v3 1/6] spapr: update spapr hotplug documentation Michael Roth
2016-10-27 2:20 ` [Qemu-devel] [PATCH v3 2/6] spapr_events: add support for dedicated hotplug event source Michael Roth
2016-10-27 2:20 ` [Qemu-devel] [PATCH v3 3/6] spapr: add hotplug interrupt machine options Michael Roth
2016-10-27 2:20 ` [Qemu-devel] [PATCH v3 4/6] spapr: Add DRC count indexed hotplug identifier type Michael Roth
2016-10-27 2:20 ` [Qemu-devel] [PATCH v3 5/6] spapr: use count+index for memory hotplug Michael Roth
2016-10-27 2:20 ` [Qemu-devel] [PATCH v3 6/6] spapr: Memory hot-unplug support Michael Roth
2016-10-27 9:26 ` [Qemu-devel] [PATCH v3 0/6] spapr: dedicated hotplug events and memory unplug support 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=1477534830-25495-1-git-send-email-mdroth@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=jallen@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--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).