From: Laurent Dufour <ldufour@linux.ibm.com>
To: Nathan Lynch <nathanl@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries: read the lpar name from the firmware
Date: Wed, 1 Dec 2021 19:00:24 +0100 [thread overview]
Message-ID: <8027ed39-3e71-a560-10c2-0ca70962ffa7@linux.ibm.com> (raw)
In-Reply-To: <60df1f67-dc37-f891-3c83-aba5a15bdddc@linux.ibm.com>
On 01/12/2021, 16:57:06, Laurent Dufour wrote:
> On 01/12/2021, 16:30:29, Nathan Lynch wrote:
>> Laurent Dufour <ldufour@linux.ibm.com> writes:
>>> The LPAR name may be changed after the LPAR has been started in the HMC.
>>> In that case lparstat command is not reporting the updated value because it
>>> reads it from the device tree which is read at boot time.
>> Could lparstat be changed to make the appropriate get-system-parameter
>> call via librtas, avoiding a kernel change?
>
> You're right, I could do that directly in lparstat without changes in the
> kernel.
Indeed, that's not so easy because the RTAS syscall can only be called by
privileged users, even to read some parameters.
So to have the lparstat command reporting the updated LPAR name, the only
way is to report that value in /proc/powerpc/lparcfg.
Furthermore, this would make sense to have this value reported in this file.
That's being said, I'll send a v2 to align the property title to the
existing "partition_id", naming it "partition_name".
prev parent reply other threads:[~2021-12-01 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 14:48 [PATCH] powerpc/pseries: read the lpar name from the firmware Laurent Dufour
2021-12-01 15:30 ` Nathan Lynch
2021-12-01 15:57 ` Laurent Dufour
2021-12-01 18:00 ` Laurent Dufour [this message]
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=8027ed39-3e71-a560-10c2-0ca70962ffa7@linux.ibm.com \
--to=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathanl@linux.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).