public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Alexandre Chartre <alexandre.chartre@oracle.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	peterz@infradead.org
Subject: Re: [PATCH v4 00/28] objtool: Function validation tracing
Date: Mon, 17 Nov 2025 09:42:10 +0000	[thread overview]
Message-ID: <20251117094210.3c3e4f40@pumpkin> (raw)
In-Reply-To: <d13e2693-125e-4ab9-983a-f83b09e8acb4@oracle.com>

On Mon, 17 Nov 2025 08:50:45 +0100
Alexandre Chartre <alexandre.chartre@oracle.com> wrote:

> On 11/14/25 22:34, Josh Poimboeuf wrote:
...
> David raises the issue that a side-by-side display requires a large window.
> 
> The compact display could be like this:
> 
> Alternative with single instruction:
> 
>    bb8:  do_one_initcall+0x1a8    <alternative.bb8>
>                                   = callq  *0x0(%rip)        # 0xbbe <pv_ops+0xf8>    (if default)
>                                   = sti                                               (if !X86_FEATURE_XENPV)
>                                   = callq  BUG_func                                   (if +X86_FEATURE_ALWAYS)
> 
> Alternative with multiple instructions:
> 
>    82e7:  __switch_to_asm+0x27    <alternative.82e7>
>                                   = DEFAULT
>    82e7:  __switch_to_asm+0x27    | jmp    0x8312 <__switch_to_asm+0x52>
>                                   |
>                                   = !X86_FEATURE_ALWAYS
>    82e7:  __switch_to_asm+0x27    | NOP1
>    82e8:  __switch_to_asm+0x28    | NOP1
>    82e9:  __switch_to_asm+0x29    | callq  0x82ef <__switch_to_asm+0x2f>
>    82ee:  __switch_to_asm+0x2e    | int3
>    82ef:  __switch_to_asm+0x2f    | add    $0x8,%rsp
>    82f3:  __switch_to_asm+0x33    | lfence
>                                   |
>                                   = X86_FEATURE_RSB_CTXSW
>    82e7:  __switch_to_asm+0x27    | mov    $0x10,%r12
>    82ee:  __switch_to_asm+0x2e    | callq  0x82f4 <__switch_to_asm+0x34>
>    82f3:  __switch_to_asm+0x33    | int3
>    82f4:  __switch_to_asm+0x34    | callq  0x82fa <__switch_to_asm+0x3a>
>    82f9:  __switch_to_asm+0x39    | int3
>    82fa:  __switch_to_asm+0x3a    | add    $0x10,%rsp
>    82fe:  __switch_to_asm+0x3e    | dec    %r12
>    8301:  __switch_to_asm+0x41    | jne    0x82ee <__switch_to_asm+0x2e>
>    8303:  __switch_to_asm+0x43    | lfence
>    8306:  __switch_to_asm+0x46    | movq   $0xffffffffffffffff,%gs:0x0(%rip)        # 0x20b <__x86_call_depth>

That does looks better.
Although I think there ought to be some indication of the 31 NOP bytes
at the end of the middle alternative.

I'd also decode those callq as 'callq .+6' - not sure what other people think?
It is rather specific to that code.

	David



  reply	other threads:[~2025-11-17  9:42 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:48 [PATCH v4 00/28] objtool: Function validation tracing Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 01/28] objtool: Move disassembly functions to a separated file Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 02/28] objtool: Create disassembly context Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 03/28] objtool: Disassemble code with libopcodes instead of running objdump Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 04/28] tool build: Remove annoying newline in build output Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 05/28] objtool: Print symbol during disassembly Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 06/28] objtool: Store instruction disassembly result Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 07/28] objtool: Disassemble instruction on warning or backtrace Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 08/28] objtool: Extract code to validate instruction from the validate branch loop Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 09/28] objtool: Record symbol name max length Alexandre Chartre
2025-11-13 16:48 ` [PATCH v4 10/28] objtool: Add option to trace function validation Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 11/28] objtool: Trace instruction state changes during " Alexandre Chartre
2025-11-14 21:21   ` Josh Poimboeuf
2025-11-17  7:33     ` Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 12/28] objtool: Improve register reporting " Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 13/28] objtool: Identify the different types of alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 14/28] objtool: Improve tracing of alternative instructions Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 15/28] objtool: Do not validate IBT for .return_sites and .call_sites Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 16/28] objtool: Add the --disas=<function-pattern> action Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 17/28] objtool: Print headers for alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 18/28] objtool: Disassemble group alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 19/28] objtool: Print addresses with alternative instructions Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 20/28] objtool: Disassemble exception table alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 21/28] objtool: Disassemble jump " Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 22/28] objtool: Fix address references in alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 23/28] objtool: Provide access to feature and flags of group alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 24/28] objtool: Function to get the name of a CPU feature Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 25/28] objtool: Improve naming of group alternatives Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 26/28] objtool: Get the destination name of a PV call Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 27/28] objtool: Improve the disassembly of the pv_ops call Alexandre Chartre
2025-11-15  1:34   ` kernel test robot
2025-11-17  7:37     ` Alexandre Chartre
2025-11-13 16:49 ` [PATCH v4 28/28] objtool: Print single line for alternatives with one instruction Alexandre Chartre
2025-11-13 19:55 ` [PATCH v4 00/28] objtool: Function validation tracing David Laight
2025-11-14  8:53   ` Alexandre Chartre
2025-11-14  1:48 ` Josh Poimboeuf
2025-11-14  9:56   ` Alexandre Chartre
2025-11-14 21:34     ` Josh Poimboeuf
2025-11-17  7:50       ` Alexandre Chartre
2025-11-17  9:42         ` David Laight [this message]
2025-11-17  9:47           ` Alexandre Chartre
2025-11-17 12:37             ` David Laight
2025-11-17 13:11               ` Alexandre Chartre
2025-11-17 22:09                 ` David Laight
2025-11-17 22:38                   ` Josh Poimboeuf
2025-11-18  9:58                     ` David Laight
2025-11-18  7:19                   ` Alexandre Chartre
2025-11-18  9:12                     ` Peter Zijlstra
2025-11-18 11:39                       ` Alexandre Chartre

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=20251117094210.3c3e4f40@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=alexandre.chartre@oracle.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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