public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	x86@kernel.org
Subject: Re: [tip: objtool/urgent] objtool: Consolidate annotation macros
Date: Wed, 3 Dec 2025 19:48:06 +0100	[thread overview]
Message-ID: <aTCF5rABohJTVCVl@gmail.com> (raw)
In-Reply-To: <CAHk-=wjc4BeSu7dHB=5AuQNWQ=sOGAuH4j0=uRwsGyiSo+m+bw@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Wed, 3 Dec 2025 at 08:57, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Find below a diff of the arch/x86/kernel/process.s output
> > of your tree versus current tip:objtool/urgent.
>
> Yeah, just a single example would have been sufficient, ie a simple
>
>    Turn
>
>         911:
>                .pushsection .discard.annotate_insn,"M", @progbits, 8
>                .long 911b - .
>                .long 1
>                .popsection
>                jmp __x86_return_thunk
>
>   Into
>
>         911: .pushsection ".discard.annotate_insn", "M", @progbits, 8;
> .long 911b - .; .long 1; .popsection
>         jmp __x86_return_thunk

I ended up rebasing the commit after all and added your example,
because seeing it written out triggered further enhancements:

> and btw, the quotes around the section name are not necessary afaik.
>
> Also, I have to say that being mergeable is a bit annoying here:
> without that, we could drop the "@progbits, 8" parts too which is just
> strange noise.  Is the mergeability really a win? Because I'd assume
> that it's never *actually* merged, since the expression "911b-." ends
> up being a unique value?
>
> What am I missing? It *feels* like this should just all be
>
>         911: .pushsection .discard.annotate_insn ; .long 911b - .;
> .long 1; .popsection
>         jmp __x86_return_thunk
>
> instead. But it's entirely possible I'm not seeing the reason here...

Thanks,

	Ingo

  parent reply	other threads:[~2025-12-03 18:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 17:59 [PATCH v2 0/4] objtool: Improve code generation for annotation macros Josh Poimboeuf
2025-12-02 17:59 ` [PATCH v2 1/4] x86/alternative: Remove ANNOTATE_DATA_SPECIAL usage Josh Poimboeuf
2025-12-03 16:40   ` [tip: objtool/urgent] " tip-bot2 for Josh Poimboeuf
2025-12-02 17:59 ` [PATCH v2 2/4] x86/asm: " Josh Poimboeuf
2025-12-03 16:40   ` [tip: objtool/urgent] " tip-bot2 for Josh Poimboeuf
2025-12-02 17:59 ` [PATCH v2 3/4] objtool: Consolidate annotation macros Josh Poimboeuf
2025-12-03 16:40   ` [tip: objtool/urgent] " tip-bot2 for Josh Poimboeuf
2025-12-03 16:49     ` Linus Torvalds
2025-12-03 16:57       ` Ingo Molnar
2025-12-03 17:20         ` Josh Poimboeuf
2025-12-03 17:21         ` Linus Torvalds
2025-12-03 17:44           ` Linus Torvalds
2025-12-03 17:51             ` Josh Poimboeuf
2025-12-03 18:07               ` [PATCH] objtool: More annotation code generation tweaks Josh Poimboeuf
2025-12-03 18:48                 ` [tip: objtool/urgent] objtool: Simplify .annotate_insn code generation output some more tip-bot2 for Josh Poimboeuf
2025-12-03 17:46           ` [tip: objtool/urgent] objtool: Consolidate annotation macros Josh Poimboeuf
2025-12-03 18:41             ` Linus Torvalds
2025-12-03 19:17               ` Josh Poimboeuf
2025-12-03 19:24                 ` Linus Torvalds
2025-12-03 18:48           ` Ingo Molnar [this message]
2025-12-03 18:48   ` tip-bot2 for Josh Poimboeuf
2025-12-02 17:59 ` [PATCH v2 4/4] objtool: Remove newlines and tabs from " Josh Poimboeuf
2025-12-03 16:40   ` [tip: objtool/urgent] " tip-bot2 for Josh Poimboeuf
2025-12-03 18:48   ` tip-bot2 for Josh Poimboeuf

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=aTCF5rABohJTVCVl@gmail.com \
    --to=mingo@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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