From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Sathvika Vasireddy <sv@linux.ibm.com>
Cc: nathan@kernel.org, nsc@kernel.org, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, jpoimboe@kernel.org,
ojeda@kernel.org, masahiroy@kernel.org, lossin@kernel.org,
tamird@kernel.org, thomas.weissschuh@linutronix.de,
rostedt@goodmis.org, ihor.solodrai@linux.dev, thuth@redhat.com,
pmladek@suse.com, aliceryhl@google.com, elver@google.com,
kees@kernel.org, legion@kernel.org, ardb@kernel.org,
yuxuan.zuo@outlook.com, alexghiti@rivosinc.com,
alexandre.chartre@oracle.com, bp@alien8.de,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v1 1/6] objtool/powerpc: Add build-time fixup of alternate feature branch targets
Date: Tue, 5 May 2026 17:48:32 +0200 [thread overview]
Message-ID: <669fbc9a-a243-43e8-8888-93bfb9d6ee12@kernel.org> (raw)
In-Reply-To: <20260505144949.GO3102924@noisy.programming.kicks-ass.net>
Le 05/05/2026 à 16:49, Peter Zijlstra a écrit :
> On Tue, May 05, 2026 at 04:45:39PM +0200, Peter Zijlstra wrote:
>> On Tue, May 05, 2026 at 02:16:23PM +0530, Sathvika Vasireddy wrote:
>>> switch (opcode) {
>>> + case 16:
>>
>> Like case 18 below, this wants a comment describing which instruction
>> this is; bclr ?
No, it is bc/bca/bcl/bcla, it is quite similar to type 18 which is
b/ba/bl/bla, but that's a conditional branch to a 14-bit offset while
type 18 is a non-conditional branch to a 24-bit offset (10 bits are the
conditional in the bc, hence the reduced offset size).
>
> Also, isn't that typically used for return, suggesting at least
> something should have INSN_RETURN on?
>
bclr (which is the return INSN_RETURN) has type 19
By the way you can have a look at
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/bfa8364da047d8610a09458a1cd924a0566aedbb.1736955567.git.christophe.leroy@csgroup.eu/
That patch has all the objtool decoding. By the way objtool is missing a
INSN_CONDITIONAL_RETURN, also see
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/537e5d8f181b1f1c2b8918f1aefa1dba3f972c03.1736955567.git.christophe.leroy@csgroup.eu/
>>> + if (ins & 1)
>>> + typ = INSN_OTHER;
>>> + else
>>> + typ = INSN_JUMP_CONDITIONAL;
>>> + imm = ins & 0xfffc;
>>> + if (imm & 0x8000)
>>> + imm -= 0x10000;
>>> + insn->immediate = imm | aa;
>>> + break;
>>> +
>>> case 18: /* b[l][a] */
>>> if (ins == 0x48000005) /* bl .+4 */
>>> typ = INSN_OTHER;
next prev parent reply other threads:[~2026-05-05 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 8:46 [PATCH v1 0/6] objtool: Fixup alternate feature relative addresses Sathvika Vasireddy
2026-05-05 8:46 ` [PATCH v1 1/6] objtool/powerpc: Add build-time fixup of alternate feature branch targets Sathvika Vasireddy
2026-05-05 14:45 ` Peter Zijlstra
2026-05-05 14:49 ` Peter Zijlstra
2026-05-05 15:48 ` Christophe Leroy (CS GROUP) [this message]
2026-05-05 15:56 ` Segher Boessenkool
2026-05-05 8:46 ` [PATCH v1 2/6] objtool: Set ELF_F_LAYOUT flag to preserve vmlinux segment layout Sathvika Vasireddy
2026-05-05 8:46 ` [PATCH v1 3/6] objtool: Fix "can't find starting instruction" warnings on vmlinux Sathvika Vasireddy
2026-05-05 8:46 ` [PATCH v1 4/6] objtool/powerpc: Skip jump destination analysis and unnanotated intra-function call warnings for --ftr-fixup Sathvika Vasireddy
2026-05-05 8:46 ` [PATCH v1 5/6] kbuild: Add objtool integration for PowerPC feature fixups Sathvika Vasireddy
2026-05-05 8:46 ` [PATCH v1 6/6] powerpc: Enable build-time feature fixup processing by default Sathvika Vasireddy
2026-05-05 9:05 ` [PATCH v1 0/6] objtool: Fixup alternate feature relative addresses Christophe Leroy (CS GROUP)
2026-05-05 11:40 ` Peter Zijlstra
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=669fbc9a-a243-43e8-8888-93bfb9d6ee12@kernel.org \
--to=chleroy@kernel.org \
--cc=alexandre.chartre@oracle.com \
--cc=alexghiti@rivosinc.com \
--cc=aliceryhl@google.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=elver@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=legion@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lossin@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=masahiroy@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=npiggin@gmail.com \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sv@linux.ibm.com \
--cc=tamird@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=thuth@redhat.com \
--cc=yuxuan.zuo@outlook.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