From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Geoff Levand <geoff@infradead.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/ps3: Use cpu_relax() in ps3_create_spu()
Date: Fri, 31 Jul 2026 09:09:29 +0200 [thread overview]
Message-ID: <1024f0e7-b9b5-4f5d-b0f5-5e7f08c51cbe@kernel.org> (raw)
In-Reply-To: <20260720231153.116827-2-thorsten.blum@linux.dev>
Le 21/07/2026 à 01:11, Thorsten Blum a écrit :
> Use cpu_relax() to wait for the execution status SPE_EX_STATE_EXECUTED.
> Drop the comments while at it.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
> ---
> arch/powerpc/platforms/ps3/spu.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/arch/powerpc/platforms/ps3/spu.c b/arch/powerpc/platforms/ps3/spu.c
> index e4e0b45e1b9d..8545c72385de 100644
> --- a/arch/powerpc/platforms/ps3/spu.c
> +++ b/arch/powerpc/platforms/ps3/spu.c
> @@ -13,6 +13,7 @@
> #include <linux/export.h>
> #include <linux/io.h>
> #include <linux/mm.h>
> +#include <linux/processor.h>
>
> #include <asm/spu.h>
> #include <asm/spu_priv1.h>
> @@ -363,12 +364,9 @@ static int __init ps3_create_spu(struct spu *spu, void *data)
> if (result)
> goto fail_enable;
>
> - /* Make sure the spu is in SPE_EX_STATE_EXECUTED. */
> -
> - /* need something better here!!! */
> - while (in_be64(&spu_pdata(spu)->shadow->spe_execution_status)
> - != SPE_EX_STATE_EXECUTED)
> - (void)0;
> + while (in_be64(&spu_pdata(spu)->shadow->spe_execution_status) !=
> + SPE_EX_STATE_EXECUTED)
> + cpu_relax();
>
> return result;
>
prev parent reply other threads:[~2026-07-31 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 23:11 [PATCH] powerpc/ps3: Use cpu_relax() in ps3_create_spu() Thorsten Blum
2026-07-31 7:09 ` Christophe Leroy (CS GROUP) [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=1024f0e7-b9b5-4f5d-b0f5-5e7f08c51cbe@kernel.org \
--to=chleroy@kernel.org \
--cc=geoff@infradead.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=thorsten.blum@linux.dev \
/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