All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH RFC 0/5] x86/asm: Improve code generation
Date: Tue,  8 Apr 2025 01:21:13 -0700	[thread overview]
Message-ID: <cover.1744098446.git.jpoimboe@kernel.org> (raw)

Some various improvements for inline asm code generation.

The "RFC" is really patches 4 and 5, they propose a more readable format
for alternatives and objtool annotations.  Bikeshedding welcome.

If a general format is agreed upon, we could do similar for other
annotations like WARN/BUG, static branches/calls, etc.

Josh Poimboeuf (5):
  objtool: Remove ANNOTATE_IGNORE_ALTERNATIVE from CLAC/STAC
  objtool, x86/hweight: Remove ANNOTATE_IGNORE_ALTERNATIVE
  noinstr: Use asm_inline() in instrumentation_{begin,end}()
  x86/alternative: Improve code generation readability
  objtool: Improve code generation readability

 arch/x86/include/asm/alternative.h  | 88 ++++++++++++++++++--------
 arch/x86/include/asm/arch_hweight.h |  6 +-
 arch/x86/include/asm/smap.h         | 12 ++--
 include/linux/instrumentation.h     |  4 +-
 include/linux/objtool.h             | 97 ++++++++++++++---------------
 tools/objtool/check.c               | 30 ++++++++-
 6 files changed, 149 insertions(+), 88 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-04-08  8:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  8:21 Josh Poimboeuf [this message]
2025-04-08  8:21 ` [PATCH RFC 1/5] objtool: Remove ANNOTATE_IGNORE_ALTERNATIVE from CLAC/STAC Josh Poimboeuf
2025-04-08 18:07   ` Linus Torvalds
2025-04-08 20:45   ` [tip: objtool/urgent] " tip-bot2 for Josh Poimboeuf
2025-04-08  8:21 ` [PATCH RFC 2/5] objtool, x86/hweight: Remove ANNOTATE_IGNORE_ALTERNATIVE Josh Poimboeuf
2025-04-08  8:21 ` [PATCH RFC 3/5] noinstr: Use asm_inline() in instrumentation_{begin,end}() Josh Poimboeuf
2025-04-08  8:30   ` Ingo Molnar
2025-04-08 11:10     ` Uros Bizjak
2025-04-08 16:46       ` Josh Poimboeuf
2025-04-08  8:21 ` [PATCH RFC 4/5] x86/alternative: Improve code generation readability Josh Poimboeuf
2025-04-09 14:38   ` Peter Zijlstra
2025-04-09 17:41     ` Josh Poimboeuf
2025-04-09 18:02       ` Linus Torvalds
2025-04-09 19:51         ` Josh Poimboeuf
2025-04-09 21:20           ` Linus Torvalds
2025-04-09 21:27             ` Josh Poimboeuf
2025-04-09 21:55               ` Josh Poimboeuf
2025-04-16 23:30         ` Josh Poimboeuf
2025-04-08  8:21 ` [PATCH RFC 5/5] objtool: " Josh Poimboeuf
2025-04-09 14: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=cover.1744098446.git.jpoimboe@kernel.org \
    --to=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.