From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Michael Bringmann <mwb@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
John Allen <jallen@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Subject: [RFC 0/4] powerpc/drcinfo: Fix bugs 'ibm,drc-info' property
Date: Thu, 15 Feb 2018 15:53:58 -0600 [thread overview]
Message-ID: <531f98fb-a29b-53e2-e7d5-870a531b76fd@linux.vnet.ibm.com> (raw)
This patch set corrects some errors and omissions in the previous
set of patches adding support for the "ibm,drc-info" property to
powerpc systems.
Unfortunately, some errors in the previous patch set break things
in some of the DLPAR operations. In particular when attempting to
hot-add a new CPU or set of CPUs, the original patch failed to
properly calculate the available resources, and aborted the operation.
In addition, the original set missed several opportunities to compress
and reuse common code, especially, in the area of device processing.
Signed-off-by: Michael W. Bringmann <mwb@linux.vnet.ibm.com>
next reply other threads:[~2018-02-15 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 21:53 Michael Bringmann [this message]
2018-02-15 21:54 ` [RFC 1/4] powerpc/hotplug/drcinfo: Fix bugs parsing ibm,drc-info structs Michael Bringmann
2018-02-15 21:55 ` [RFC 2/4] powerpc/hotplug/drcinfo: Provide common parser for ibm,drc-info Michael Bringmann
2018-02-15 21:56 ` [RFC 4/4] powerpc/hotplug/drcinfo: Improve code for ibm,drc-info device processing Michael Bringmann
2018-02-15 23:52 ` [RFC 3/4] powerpc/hotplug/drcinfo: Fix hot-add CPU issues Michael Bringmann
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=531f98fb-a29b-53e2-e7d5-870a531b76fd@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.com \
/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).