From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Shivang Upadhyay <shivangu@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
chleroy@kernel.org, adri.vero.dev@gmail.com,
adityag@linux.ibm.com, anushree.mathur@linux.vnet.ibm.com
Subject: Re: [PATCH] ppc/fadump: collect dump if the collected size is lesser than reserved
Date: Sun, 19 Jul 2026 12:39:01 +0530 [thread overview]
Message-ID: <446c84c2-8639-4ecb-8a46-1e203a166e46@linux.ibm.com> (raw)
In-Reply-To: <20260714173010.615682-1-shivangu@linux.ibm.com>
Could you please reword the commit title to make it a bit clearer?
On 14/07/26 23:00, Shivang Upadhyay wrote:
> When a machine is subjected to CPUs add/remove, using dlpar
> operations, the number of collected CPU_NOTES can change.
> As per PAPR, collected dump size should not be more than
> allocated size. Reflecting the same in source.
Can you add more details about the problem you are trying to solve
with this patch and how.
Adding the error message and scenario would be really helpful in
understanding the problem.
Can you add Closes tag if it is reported upstream and if possible fixes
tag too.
> Signed-off-by: Shivang Upadhyay <shivangu@linux.ibm.com>
> ---
> arch/powerpc/platforms/pseries/rtas-fadump.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/platforms/pseries/rtas-fadump.c b/arch/powerpc/platforms/pseries/rtas-fadump.c
> index 3bb4ac2ab6cc..19a5adaf326b 100644
> --- a/arch/powerpc/platforms/pseries/rtas-fadump.c
> +++ b/arch/powerpc/platforms/pseries/rtas-fadump.c
> @@ -469,7 +469,8 @@ static int __init rtas_fadump_process(struct fw_dump *fadump_conf)
> pr_err("Dump taken by platform is not valid (%d)\n", i);
> rc = -EINVAL;
> }
> - if (fdm_active->rgn[i].bytes_dumped != fdm_active->rgn[i].source_len) {
> + if (be64_to_cpu(fdm_active->rgn[i].bytes_dumped)
> + > be64_to_cpu(fdm_active->rgn[i].source_len)) {
Can you please share your observations about `bytes_dump` for both QEMU
and a
real system (LPAR) where the number of online CPUs is not equal to the
maximum
number of CPUs?
I agree that you're making these changes to comply with PAPR, but since
this has been
working for so long, it would be good to have all the data before making
this change.
- Sourabh Jain
> pr_err("Dump taken by platform is incomplete (%d)\n", i);
> rc = -EINVAL;
> }
prev parent reply other threads:[~2026-07-19 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 17:30 [PATCH] ppc/fadump: collect dump if the collected size is lesser than reserved Shivang Upadhyay
2026-07-19 7:09 ` Sourabh Jain [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=446c84c2-8639-4ecb-8a46-1e203a166e46@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=adri.vero.dev@gmail.com \
--cc=anushree.mathur@linux.vnet.ibm.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shivangu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.