LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shivang Upadhyay <shivangu@linux.ibm.com>
To: Sourabh Jain <sourabhjain@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: Wed, 29 Jul 2026 13:59:49 +0530	[thread overview]
Message-ID: <dfb0705e5b3a7a3f2f06d842b68910e6eca742f9.camel@linux.ibm.com> (raw)
In-Reply-To: <93bd50eb-0205-4ed6-a3cb-a29bda61db3d@linux.ibm.com>

On Wed, 2026-07-29 at 13:43 +0530, Sourabh Jain wrote:
> > > But the firmware not copying the entire Real Mode memory is also
> > > a
> > > problem for
> > > the kernel, isn't it?
> > > 
> > I think it should be fine. Firmware will report it status flags,
> > right?
> 
> I don't know. Does PAPR says anything about the error code
> corresponds
> to when memory to not copied completely?

As much as i could search, I didn't see this case metioned there. I
think if, fw is failing to copy full content it should report one of
the below errors.

- copy from [x...x+size] to [y...y+size]. 
- x + x_i is not valid 
  - leads to invalid source address.
- y + y+i is not valid
  - leads to invalid dest address.


But anyways, As the source/proper description is not available, we
can't prove much here. Would it be appropriate, if I just make this
case for CPU_DATA area?

~Shivang.


      reply	other threads:[~2026-07-29  8:30 UTC|newest]

Thread overview: 9+ 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
2026-07-22  9:11   ` Shivang Upadhyay
2026-07-29  3:44     ` Sourabh Jain
2026-07-29  6:06       ` Shivang Upadhyay
2026-07-29  6:28         ` Sourabh Jain
2026-07-29  7:00           ` Shivang Upadhyay
2026-07-29  8:13             ` Sourabh Jain
2026-07-29  8:29               ` Shivang Upadhyay [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=dfb0705e5b3a7a3f2f06d842b68910e6eca742f9.camel@linux.ibm.com \
    --to=shivangu@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=sourabhjain@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