From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 5/6] powerpc/pseries: Add CPU dlpar add functionality
Date: Tue, 1 Dec 2015 15:00:35 -0600 [thread overview]
Message-ID: <565E0A73.8040806@linux.vnet.ibm.com> (raw)
In-Reply-To: <1448514803.9839.9.camel@ellerman.id.au>
On 11/25/2015 11:13 PM, Michael Ellerman wrote:
> On Tue, 2015-10-27 at 13:27 -0500, Nathan Fontenot wrote:
>
>> Add the ability to hotplug add cpus via rtas hotplug events by either
>> specifying the drc index of the CPU to add, or providing a count of the
>> number of CPUs to add.
>
> So I just tried running this on my system, without doing anything on the HMC.
>
> I have:
>
> # lsprop /proc/device-tree/cpus/ibm,drc-indexes
> /proc/device-tree/cpus/ibm,drc-indexes
> 00000002 10000000 10000002
>
> So I think that says I have two cpus.
>
> The first one is already added:
>
> /proc/device-tree/cpus/PowerPC,POWER6@0/ibm,my-drc-index
> 10000000 (268435456)
>
> But can I add the second one?
>
> # echo "cpu add count 1" > dlpar
> RTAS: event: 34, Type: Platform Error, Severity: 2
> pseries-hotplug-cpu: Failed to acquire DRC, rc: -5, drc index: 10000002
> pseries-hotplug-cpu: CPU hot-add failed, removing any added CPUs
> -bash: echo: write error: Invalid argument
>
>
> Seems not. But I'm not clear why?
The add request is failing because rtas call to acquire the resource is failing.
I have seen this on many systems lately. Previously one could add and remove
CPUs (and memory) by running the drmgr command on an LPAR manually and
everything would work. It seems there are now systems (not sure if its a
firmware or HMC update) that will only allow the rtas call to acquire the
resource to succeed when the request is initiated from the HMC.
I can provide a patch for drmgr that uses the new sysfs interface so you
can drive the dlpar operations from the hmc.
>
> Adding by index doesn't work either:
>
> # echo "cpu add index 10000002" > dlpar
> pseries-hotplug-cpu: Failed to acquire DRC, rc: -1, drc index: 989682
> -bash: echo: write error: Invalid argument
>
> That's a little confusing, drc index is hex obviously.
>
> [root@p6-10-P5-E0 kernel]# echo "cpu add index 0x10000002" > dlpar
> RTAS: event: 35, Type: Platform Error, Severity: 2
> pseries-hotplug-cpu: Failed to acquire DRC, rc: -5, drc index: 10000002
> -bash: echo: write error: Invalid argument
>
>
> So that's probably all PEBKAC, but if we can make it more intutive that would be good.
I wrote the interface to take the drc index value in the format specified, so
without the 0x it assumes decimal. Should be a better error message in this case.
-Nathan
next prev parent reply other threads:[~2015-12-01 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 18:21 [PATCH v2 0/6] powerpc/pseries: Move CPU DLPAR into the kernel Nathan Fontenot
2015-10-27 18:23 ` [PATCH v2 1/6] powerpc/pseries: Consolidate CPU hotplug code to hotplug-cpu.c Nathan Fontenot
2015-10-27 18:24 ` [PATCH v2 2/6] powerpc/pseries: Factor out common cpu hotplug code Nathan Fontenot
2015-10-27 18:25 ` [PATCH v2 3/6] powerpc/pseries: Update CPU hotplug error recovery Nathan Fontenot
2015-10-27 18:26 ` [PATCH v2 4/6] powerpc/pseries: Add CPU dlpar remove functionality Nathan Fontenot
2015-11-26 5:02 ` Michael Ellerman
2015-12-01 20:51 ` Nathan Fontenot
2015-10-27 18:27 ` [PATCH v2 5/6] powerpc/pseries: Add CPU dlpar add functionality Nathan Fontenot
2015-11-26 5:13 ` Michael Ellerman
2015-12-01 21:00 ` Nathan Fontenot [this message]
2015-10-27 18:28 ` [PATCH v2 6/6] powerpc/pseries: Enable kernel CPU dlpar from sysfs Nathan Fontenot
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=565E0A73.8040806@linux.vnet.ibm.com \
--to=nfont@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).