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, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/misc changes for v5.7
Date: Tue, 31 Mar 2020 10:37:55 +0200	[thread overview]
Message-ID: <20200331083755.GA70287@gmail.com> (raw)

Linus,

Please pull the latest x86-misc-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-misc-for-linus

   # HEAD: 1032f32645f8a650edb0134d52fa085642d0a492 perf/tests: Add CET instructions to the new instructions test

Misc [ :-) ] changes:

 - extend the decoder maps with CET instructions

 - fix !vDSO corner cases


  out-of-topic modifications in x86-misc-for-linus:
  ---------------------------------------------------
  tools/testing/selftests/x86/ptrace_syscall.c# 630b99ab60aa: selftests/x86/ptrace_syscall
  tools/testing/selftests/x86/test_vdso.c# 07f24dc95dac: selftests/x86/vdso: Fix no-v
  tools/testing/selftests/x86/vdso_restorer.c# 07f24dc95dac: selftests/x86/vdso: Fix no-v

 Thanks,

	Ingo

------------------>
Adrian Hunter (1):
      perf/tests: Add CET instructions to the new instructions test

Andy Lutomirski (2):
      selftests/x86/vdso: Fix no-vDSO segfaults
      selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault

Yu-cheng Yu (1):
      x86/insn: Add Control-flow Enforcement (CET) instructions to the opcode map


 arch/x86/lib/x86-opcode-map.txt              |  17 +-
 tools/arch/x86/lib/x86-opcode-map.txt        |  17 +-
 tools/perf/arch/x86/tests/insn-x86-dat-32.c  | 112 +++++++++++++
 tools/perf/arch/x86/tests/insn-x86-dat-64.c  | 196 ++++++++++++++++++++++
 tools/perf/arch/x86/tests/insn-x86-dat-src.c | 236 +++++++++++++++++++++++++++
 tools/testing/selftests/x86/ptrace_syscall.c |   8 +-
 tools/testing/selftests/x86/test_vdso.c      |   5 +
 tools/testing/selftests/x86/vdso_restorer.c  |  15 ++
 8 files changed, 592 insertions(+), 14 deletions(-)

             reply	other threads:[~2020-03-31  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  8:37 Ingo Molnar [this message]
2020-03-31 19:15 ` [GIT PULL] x86/misc changes for v5.7 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=20200331083755.GA70287@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.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