From: Nathan Lynch <nathanl@linux.ibm.com>
To: "Nicholas Piggin" <npiggin@gmail.com>,
"Leonardo Brás" <leobras.c@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Revert "powerpc/rtas: Implement reentrant rtas call"
Date: Wed, 21 Sep 2022 10:54:41 -0500 [thread overview]
Message-ID: <87fsgkrada.fsf@linux.ibm.com> (raw)
In-Reply-To: <CN0XB6PRTPP7.W10Z5R1QNLZC@bobo>
"Nicholas Piggin" <npiggin@gmail.com> writes:
> On Mon Sep 19, 2022 at 11:51 PM AEST, Nathan Lynch wrote:
>> > I wonder - would it be worth making the panic path use a separate
>> > "emergency" rtas_args buffer as well? If a CPU is actually "stuck" in
>> > RTAS at panic time, then leaving rtas.args untouched might make the
>> > ibm,int-off, ibm,set-xive, ibm,os-term, and any other RTAS calls we
>> > incur on the panic path more likely to succeed.
>
> Yeah I think that's probably not a bad idea. Not sure if you've got the
> bandwidth to take on doing the patch but be my guest if you do :)
> Otherwise we can file it in github issues.
Not sure I'll be able to work it soon. I filed
https://github.com/linuxppc/issues/issues/435
next prev parent reply other threads:[~2022-09-21 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 22:01 [PATCH] Revert "powerpc/rtas: Implement reentrant rtas call" Nathan Lynch
2022-09-08 7:56 ` Laurent Dufour
[not found] ` <1d76891ee052112ee1547a4027e358d5cbcac23d.camel@gmail.com>
2022-09-09 14:04 ` Nathan Lynch
2022-09-12 15:22 ` Leonardo Brás
2022-09-12 19:58 ` Nathan Lynch
2022-09-13 17:39 ` Leonardo Brás
2022-09-16 1:31 ` Nicholas Piggin
2022-09-16 21:56 ` Nathan Lynch
2022-09-19 13:51 ` Nathan Lynch
2022-09-19 23:45 ` Michael Ellerman
2022-09-20 3:54 ` Nicholas Piggin
2022-09-21 15:54 ` Nathan Lynch [this message]
2023-04-14 14:20 ` Michal Suchánek
2023-04-17 13:55 ` Nathan Lynch
2022-09-23 10:57 ` 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=87fsgkrada.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=leobras.c@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).