From: Michael Ellerman <mpe@ellerman.id.au>
To: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/3] powerpc/ppc-opcode: Define and use PPC_RAW_TRAP() and PPC_RAW_TW()
Date: Wed, 03 Aug 2022 20:38:48 +1000 [thread overview]
Message-ID: <87les5a9xj.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <1659513939.dxqqwb8mat.naveen@linux.ibm.com>
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com> writes:
> Christophe Leroy wrote:
>> Add and use PPC_RAW_TRAP() instead of opencoding.
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> ---
>> arch/powerpc/include/asm/ppc-opcode.h | 2 ++
>> arch/powerpc/include/asm/probes.h | 3 ++-
>> arch/powerpc/xmon/xmon.c | 2 +-
>> 3 files changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/ppc-opcode.h b/arch/powerpc/include/asm/ppc-opcode.h
>> index 89beabf5325c..5527a955fb4a 100644
>> --- a/arch/powerpc/include/asm/ppc-opcode.h
>> +++ b/arch/powerpc/include/asm/ppc-opcode.h
>> @@ -581,6 +581,8 @@
>>
>> #define PPC_RAW_BRANCH(offset) (0x48000000 | PPC_LI(offset))
>> #define PPC_RAW_BL(offset) (0x48000001 | PPC_LI(offset))
>> +#define PPC_RAW_TW(t0, a, b) (0x7f000008 | ___PPC_RS(t0) | ___PPC_RA(a) | ___PPC_RB(b))
>
> Shouldn't that be 0x7c000008 ?
Yes, my script agrees.
https://github.com/mpe/misc-scripts/blob/master/ppc/ppc-instruction-encode
$ ./ppc-instruction-encode 0:31 6:t0 11:ra 16:rb 21:4 31:
.long 0x7c000008
t0 << 21
ra << 16
rb << 11
I guess the only user is PPC_RAW_TRAP() which passes t0 = 31, so that's
why nothing has broken.
Send a fixup? :)
cheers
next prev parent reply other threads:[~2022-08-03 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 14:55 [PATCH 1/3] powerpc/probes: Remove ppc_opcode_t Christophe Leroy
2022-07-07 14:55 ` [PATCH 2/3] powerpc/ppc-opcode: Define and use PPC_RAW_TRAP() and PPC_RAW_TW() Christophe Leroy
2022-08-03 8:06 ` Naveen N. Rao
2022-08-03 10:38 ` Michael Ellerman [this message]
2022-07-07 14:55 ` [PATCH 3/3] powerpc/ppc-opcode: Define and use PPC_RAW_SETB() Christophe Leroy
2022-07-29 13:02 ` [PATCH 1/3] powerpc/probes: Remove ppc_opcode_t 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=87les5a9xj.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=paulus@samba.org \
/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