From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: mpe@ellerman.id.au
Cc: nathanl@linux.ibm.com, tyreld@linux.ibm.com,
sshegde@linux.ibm.com, npiggin@gmail.com, mahesh@linux.ibm.com,
naveen.n.rao@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/2] powerpc/pseries: Fixes for lparstat boot reports
Date: Fri, 12 Apr 2024 14:50:45 +0530 [thread overview]
Message-ID: <20240412092047.455483-1-sshegde@linux.ibm.com> (raw)
Currently lparstat reports which shows since LPAR boot are wrong for
some fields. There is a need for storing the PIC(Pool Idle Count) at
boot for accurate reporting. PATCH 1 Does that.
While there, it was noticed that hcall return value is long and both
h_get_ppp and h_get_mpp could set the uninitialized values if the hcall
fails. PATCH 2 does that.
v1 -> v2:
- Nathan pointed out the issues surrounding the h_pic call. Addressed
those.
- Added a pr_debug if h_pic fails during lparcfg_init
- If h_pic fails while reading lparcfg, related files are not exported.
- Added failure checks for h_get_mpp, h_get_ppp calls as well.
v1: https://lore.kernel.org/all/20240405101340.149171-1-sshegde@linux.ibm.com/
Shrikanth Hegde (2):
powerpc/pseries: Add pool idle time at LPAR boot
powerpc/pseries: Add fail related checks for h_get_mpp and h_get_ppp
arch/powerpc/include/asm/hvcall.h | 2 +-
arch/powerpc/platforms/pseries/lpar.c | 6 ++--
arch/powerpc/platforms/pseries/lparcfg.c | 45 +++++++++++++++++-------
3 files changed, 37 insertions(+), 16 deletions(-)
--
2.39.3
next reply other threads:[~2024-04-12 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 9:20 Shrikanth Hegde [this message]
2024-04-12 9:20 ` [PATCH v2 1/2] powerpc/pseries: Add pool idle time at LPAR boot Shrikanth Hegde
2024-04-12 9:20 ` [PATCH v2 2/2] powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp Shrikanth Hegde
2024-04-29 5:55 ` [PATCH v2 0/2] powerpc/pseries: Fixes for lparstat boot reports Shrikanth Hegde
2024-04-30 3:54 ` Michael Ellerman
2024-05-03 10:41 ` Michael Ellerman
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=20240412092047.455483-1-sshegde@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=tyreld@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 read-only IMAP folder(s) and NNTP newsgroup(s).