linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Scott Wood <oss@buserror.net>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, jbglaw@lug-owl.de,
	Nicholas Piggin <npiggin@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 5/5] powerpc/epapr: Don't use wrteei on non booke
Date: Thu, 16 Feb 2023 00:15:40 +0100	[thread overview]
Message-ID: <20230215231540.vmskpw33l2ctyp4c@pali> (raw)
In-Reply-To: <20221220202111.jpxsyviplco6sbsm@pali>

On Tuesday 20 December 2022 21:21:11 Pali Rohár wrote:
> On Monday 19 December 2022 19:46:00 Christophe Leroy wrote:
> > wrteei is only for booke. Use the standard mfmsr/ori/mtmsr
> > when non booke.
> > 
> > Reported-by: Jan-Benedict Glaw <jbglaw@lug-owl.de>
> > Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> > ---
> > Not sure this is needed at all, the commit that introduced the code says it is for e500, but there's no such limitation in Kconfig. Maybe we should limit all the file to CONFIG_PPC_E500
> 
> This ePAPR code is according to ePAPR v1.1. So it does not have to be
> e500 specific. But is there anything else in this category?

Scott Wood: Do you know any details about it?

> > ---
> >  arch/powerpc/kernel/epapr_hcalls.S | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/arch/powerpc/kernel/epapr_hcalls.S b/arch/powerpc/kernel/epapr_hcalls.S
> > index 69a912550577..033116e465d0 100644
> > --- a/arch/powerpc/kernel/epapr_hcalls.S
> > +++ b/arch/powerpc/kernel/epapr_hcalls.S
> > @@ -21,7 +21,13 @@ _GLOBAL(epapr_ev_idle)
> >  	ori	r4, r4,_TLF_NAPPING	/* so when we take an exception */
> >  	PPC_STL	r4, TI_LOCAL_FLAGS(r2)	/* it will return to our caller */
> >  
> > +#ifdef CONFIG_BOOKE_OR_40x
> >  	wrteei	1
> > +#else
> > +	mfmsr	r4
> > +	ori	r4, r4, MSR_EE
> > +	mtmsr	r4
> > +#endif
> >  
> >  idle_loop:
> >  	LOAD_REG_IMMEDIATE(r11, EV_HCALL_TOKEN(EV_IDLE))
> > -- 
> > 2.38.1
> > 

  reply	other threads:[~2023-02-15 23:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 18:45 [PATCH v1 1/5] powerpc/64: Set default CPU in Kconfig Christophe Leroy
2022-12-19 18:45 ` [PATCH v1 2/5] powerpc: Pass correct CPU reference to assembler Christophe Leroy
2022-12-20 20:14   ` Pali Rohár
2022-12-19 18:45 ` [PATCH v1 3/5] powerpc/64: Replace -mcpu=e500mc64 by -mcpu=e5500 Christophe Leroy
2022-12-20 20:15   ` Pali Rohár
2023-02-01 23:46     ` Pali Rohár
2023-02-03 18:23       ` Christophe Leroy
2022-12-19 18:45 ` [PATCH v1 4/5] powerpc: Remove cpu-as-y completely Christophe Leroy
2022-12-20 20:15   ` Pali Rohár
2023-02-20  6:00   ` Michael Ellerman
2024-02-16 15:25     ` Christophe Leroy
2024-02-24 23:52       ` Michael Ellerman
2022-12-19 18:46 ` [PATCH v1 5/5] powerpc/epapr: Don't use wrteei on non booke Christophe Leroy
2022-12-20 20:21   ` Pali Rohár
2023-02-15 23:15     ` Pali Rohár [this message]
2022-12-20 20:13 ` [PATCH v1 1/5] powerpc/64: Set default CPU in Kconfig Pali Rohár
2023-02-20  3:53 ` 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=20230215231540.vmskpw33l2ctyp4c@pali \
    --to=pali@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=oss@buserror.net \
    /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).