linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Borislav Petkov <bp@alien8.de>
Subject: [GIT PULL] Objtool updates for v6.1
Date: Fri, 7 Oct 2022 10:19:07 +0200	[thread overview]
Message-ID: <Yz/g+0Ar/1z1d7Uh@gmail.com> (raw)

Linus,

Please pull the latest objtool/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git objtool-core-2022-10-07

   # HEAD: 7a7621dfa417aa3715d2a3bd1bdd6cf5018274d0 objtool,x86: Teach decode about LOOP* instructions

Fairly small batch of changes:

Objtool changes for v6.1:

 - Remove the "ANNOTATE_NOENDBR on ENDBR" warning: it's not
   really useful and only found a non-bug false positive so far.

 - Properly decode LOOP/LOOPE/LOOPNE, which were missing from
   the x86 decoder. Because these instructions are rather
   ineffective, they never showed up in compiler output,
   but they are simple enough to support, so add them for
   completeness.

 - A bit more cross-arch preparatory work.

 Thanks,

	Ingo

------------------>
Chen Zhongjin (1):
      objtool: Use arch_jump_destination() in read_intra_function_calls()

Josh Poimboeuf (1):
      objtool: Remove "ANNOTATE_NOENDBR on ENDBR" warning

Peter Zijlstra (1):
      objtool,x86: Teach decode about LOOP* instructions


 tools/objtool/arch/x86/decode.c | 6 ++++++
 tools/objtool/check.c           | 5 +----
 2 files changed, 7 insertions(+), 4 deletions(-)

             reply	other threads:[~2022-10-07  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  8:19 Ingo Molnar [this message]
2022-10-10 17:22 ` [GIT PULL] Objtool updates for v6.1 pr-tracker-bot

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=Yz/g+0Ar/1z1d7Uh@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).