From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Adriano Vero <litaliano00.contact@gmail.com>,
maddy@linux.ibm.com, mpe@ellerman.id.au
Cc: npiggin@gmail.com, chleroy@kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Adriano Vero <litaliano00.contact@gmail.com>
Subject: Re: [PATCH] powerpc/fadump: Add timeout to RTAS busy-wait loops
Date: Tue, 07 Apr 2026 09:36:50 +0530 [thread overview]
Message-ID: <wlyjl8h1.ritesh.list@gmail.com> (raw)
In-Reply-To: <20260406061542.22354-1-litaliano00.contact@gmail.com>
Adriano Vero <litaliano00.contact@gmail.com> writes:
> The ibm,configure-kernel-dump RTAS call sites in
> rtas_fadump_register(), rtas_fadump_unregister(), and
> rtas_fadump_invalidate() polled indefinitely while firmware returned
> a busy status. A misbehaving or hung firmware could stall these paths
> forever, blocking fadump registration at boot or preventing clean
> teardown.
Was there an issue which you encountered? Can you share the details of
the same please?
>
> Track the accumulated delay in a total_wait counter and bail out with
> -ETIMEDOUT if it reaches RTAS_FADUMP_MAX_WAIT_MS (60 seconds) before
> firmware signals completion. This follows the bounded busy-wait pattern
> used in rtas-rtc.c.
>
> Signed-off-by: Adriano Vero <litaliano00.contact@gmail.com>
next prev parent reply other threads:[~2026-04-07 4:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 6:15 [PATCH] powerpc/fadump: Add timeout to RTAS busy-wait loops Adriano Vero
2026-04-07 4:06 ` Ritesh Harjani [this message]
2026-04-07 6:28 ` litaliano00
2026-04-13 13:50 ` Sourabh Jain
2026-04-13 21:37 ` litaliano00
2026-04-14 10:29 ` Sourabh Jain
2026-04-19 6:50 ` [PATCH v2] " Adriano Vero
2026-05-06 19:21 ` Sourabh Jain
2026-05-07 2:52 ` Adriano Vero
2026-05-07 4:07 ` Sourabh Jain
2026-05-06 22:20 ` [PATCH v3] " Adriano Vero
2026-05-07 4:15 ` Sourabh Jain
2026-05-07 8:08 ` Adriano Vero
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=wlyjl8h1.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=litaliano00.contact@gmail.com \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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.