The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Narayana Murty N <nnmlinux@linux.ibm.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>,
	mahesh@linux.ibm.com, maddy@linux.ibm.com, mpe@ellerman.id.au,
	christophe.leroy@csgroup.eu, gregkh@linuxfoundation.org,
	oohall@gmail.com, npiggin@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	tyreld@linux.ibm.com, vaibhav@linux.ibm.com, sbhat@linux.ibm.com,
	ganeshgr@linux.ibm.com, haren@linux.ibm.com, thuth@redhat.com
Subject: Re: [PATCH v2 1/5] powerpc/rtas: Handle special return format for RTAS_FN_IBM_OPEN_ERRINJCT
Date: Tue, 4 Aug 2026 11:24:20 +0530	[thread overview]
Message-ID: <402be22e-05da-4e0e-9bb1-fa37addb72c6@linux.ibm.com> (raw)
In-Reply-To: <79ade62b-6e94-4219-b7fb-95cc3b80c957@linux.ibm.com>

Hi Sourabh,

Thanks for the review.

On 07/06/26 4:49 PM, Sourabh Jain wrote:
>
>
> On 27/05/26 12:54, Narayana Murty N wrote:
>> RTAS_FN_IBM_OPEN_ERRINJCT returns results in special format:
>>    rets[0] = session token (output)
>>    rets[1] = status code
>>    rets[2..] = additional outputs (if any)
>>
>> Unlike standard RTAS calls where:
>>    rets[0] = status code
>>    rets[1..] = outputs
>>
>> This patch adds special handling for OPEN_ERRINJCT to:
>> 1. Check correct status position (rets[1]) for __fetch_rtas_last_error()
>
> You can consider fixing the same for the RTAS syscall.
>> 2. Copy all rets[0..nret-1] to outputs[] (including token at rets[0])
>> 3. Return status from rets[1] instead of rets[0]
>>
>> Reference: OpenPOWER PAPR documentation
>>        https://files.openpower.foundation/s/XFgfMaqLMD5Bcm8
>> Signed-off-by: Narayana Murty N <nnmlinux@linux.ibm.com>
>> ---
>>   arch/powerpc/kernel/rtas.c | 47 ++++++++++++++++++++++++++++++++------
>>   1 file changed, 40 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/rtas.c b/arch/powerpc/kernel/rtas.c
>> index 8d81c1e7a8db..a2dd94eed9d0 100644
>> --- a/arch/powerpc/kernel/rtas.c
>> +++ b/arch/powerpc/kernel/rtas.c
>> @@ -1183,7 +1183,7 @@ int rtas_call(int token, int nargs, int nret, 
>> int *outputs, ...)
>>       unsigned long flags;
>>       struct rtas_args *args;
>>       char *buff_copy = NULL;
>> -    int ret;
>> +    int ret = 0;
>>         if (!rtas.entry || token == RTAS_UNKNOWN_SERVICE)
>>           return -1;
>> @@ -1213,15 +1213,48 @@ int rtas_call(int token, int nargs, int nret, 
>> int *outputs, ...)
>>       va_rtas_call_unlocked(args, token, nargs, nret, list);
>>       va_end(list);
>>   +    /*
>> +     * Special handling for RTAS_FN_IBM_OPEN_ERRINJCT:
>> +     * Per PAPR, ibm,open-errinjct has a unique return format:
>> +     *   rets[0] = injection session token (output parameter)
>> +     *   rets[1] = status code
>> +     *
>> +     * This differs from standard RTAS calls which return:
>> +     *   rets[0] = status code
>> +     *   rets[1..] = output parameters
>> +     *
>> +     * We must extract status from rets[1] (not rets[0]) to correctly
>> +     * detect errors and trigger __fetch_rtas_last_error() when 
>> status == -1.
>> +     */
>>       /* A -1 return code indicates that the last command couldn't
>> -       be completed due to a hardware error. */
>
> The above comment should be moved to next if block, if (ret == -1).
>
>> -    if (be32_to_cpu(args->rets[0]) == -1)
>> +     * be completed due to a hardware error.
>> +     */
>> +    if (token == rtas_function_token(RTAS_FN_IBM_OPEN_ERRINJCT) && 
>> nret > 1)
>> +        ret = be32_to_cpu(args->rets[1]);
>> +    else if (nret > 0)
>> +        ret = be32_to_cpu(args->rets[0]);
>> +
>> +    if (ret == -1)
>>           buff_copy = __fetch_rtas_last_error(NULL);
>>   -    if (nret > 1 && outputs != NULL)
>> -        for (i = 0; i < nret-1; ++i)
>> -            outputs[i] = be32_to_cpu(args->rets[i + 1]);
>> -    ret = (nret > 0) ? be32_to_cpu(args->rets[0]) : 0;
>> +    /* Copy all return values to caller's outputs buffer if provided */
>> +    if (nret > 1 && outputs != NULL) {
>> +        if (token == rtas_function_token(RTAS_FN_IBM_OPEN_ERRINJCT)) {
>> +            /* Special case: rets[0]=token, rets[1]=status, 
>> rets[2..]=outputs */
>> +            for (i = 0; i < nret; ++i)
>> +                outputs[i] = be32_to_cpu(args->rets[i]);
>> +        } else {
>> +            /* Normal case: rets[0]=status, rets[1..]=outputs */
>> +            for (i = 0; i < nret - 1; ++i)
>> +                outputs[i] = be32_to_cpu(args->rets[i + 1]);
>
> I am surprised that status is never copied to the output buffer even 
> though it is part
> of the output as per PAPR. But status is copied for ibm,open-errinjct, 
> which is okay.
>
For normal RTAS calls, |rtas_call()|returns |rets[0]|, the firmware 
status, as its function

return value and copies only |rets[1..]|into the caller's 
|outputs[]|buffer. I intended to

preserve this existing API.

For |ibm,open-errinjct|, I will follow the same API convention: return 
the status from |rets[1]|,

copy the session token from |rets[0]|to |outputs[0]|, and copy any 
additional output values from |
|

|rets[2..]|to the subsequent entries in |outputs[]|. Therefore, the 
status does not need to

be copied into |outputs[]|.

>> +        }
>> +    } else {
>> +        /* Either no outputs to copy (nret <= 1) or caller
>> +         * didn't provide output buffer ensure ret contains
>> +         * the status code for standard RTAS calls.
>> +         */
>> +        ret = (nret > 0) ? be32_to_cpu(args->rets[0]) : 0;
>
> What is the need to find ret again? Isn't it already done above?
You are right. |ret|has already been determined above, so the 
|else|block is unnecessary.
>
>
>> +    }
>>         lockdep_unpin_lock(&rtas_lock, cookie);
>>       raw_spin_unlock_irqrestore(&rtas_lock, flags);
>


  reply	other threads:[~2026-08-04  5:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27  7:24 [PATCH v2 0/5] powerpc/pseries: Add full RTAS-based error injection support Narayana Murty N
2026-05-27  7:24 ` [PATCH v2 1/5] powerpc/rtas: Handle special return format for RTAS_FN_IBM_OPEN_ERRINJCT Narayana Murty N
2026-06-07 11:19   ` Sourabh Jain
2026-08-04  5:54     ` Narayana Murty N [this message]
2026-05-27  7:24 ` [PATCH v2 2/5] powerpc/pseries: Add RTAS error injection buffer infrastructure Narayana Murty N
2026-06-10  3:27   ` Sourabh Jain
2026-08-04  5:57     ` Narayana Murty N
2026-05-27  7:24 ` [PATCH v2 3/5] powerpc/pseries: Add RTAS error injection validation helpers Narayana Murty N
2026-06-07 12:17   ` Sourabh Jain
2026-08-04  6:07     ` Narayana Murty N
2026-05-27  7:24 ` [PATCH v2 4/5] powerpc/pseries: Implement RTAS error injection via pseries_eeh_err_inject Narayana Murty N
2026-06-07 13:35   ` Sourabh Jain
2026-08-04  6:30     ` Narayana Murty N
2026-06-10  3:45   ` Sourabh Jain
2026-08-04  6:37     ` Narayana Murty N
2026-05-27  7:24 ` [PATCH v2 5/5] powerpc/powernv: Map EEH error types to OPAL error injection types Narayana Murty N
2026-06-07 13:46   ` Sourabh Jain
2026-08-04  6:42     ` Narayana Murty N

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=402be22e-05da-4e0e-9bb1-fa37addb72c6@linux.ibm.com \
    --to=nnmlinux@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=ganeshgr@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haren@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=oohall@gmail.com \
    --cc=sbhat@linux.ibm.com \
    --cc=sourabhjain@linux.ibm.com \
    --cc=thuth@redhat.com \
    --cc=tyreld@linux.ibm.com \
    --cc=vaibhav@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