All of lore.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, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Uros Bizjak <ubizjak@gmail.com>, Brian Gerst <brgerst@gmail.com>,
	Andy Lutomirski <luto@kernel.org>
Subject: [GIT PULL] x86/entry changes for v6.7
Date: Sat, 28 Oct 2023 15:37:46 +0200	[thread overview]
Message-ID: <ZT0OqhIh/7c9IOYU@gmail.com> (raw)

Linus,

Please pull the latest x86/entry git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-entry-2023-10-28

   # HEAD: 1a09a27153f91cd7676b2d4ca574577572a8c999 x86/entry/32: Clean up syscall fast exit tests

Changes to the x86 entry code in v6.7:

 - Make IA32_EMULATION boot time configurable with
   the new ia32_emulation=<bool> boot option.

 - Clean up fast syscall return validation code: convert
   it to C and refactor the code.

 - As part of this, optimize the canonical RIP test code.

 Thanks,

	Ingo

------------------>
Brian Gerst (7):
      x86/entry/64: Remove obsolete comment on tracing vs. SYSRET
      x86/entry/compat: Combine return value test from syscall handler
      x86/entry/32: Convert do_fast_syscall_32() to bool return type
      x86/entry/32: Remove SEP test for SYSEXIT
      x86/entry/64: Convert SYSRET validation tests to C
      x86/entry/64: Use TASK_SIZE_MAX for canonical RIP test
      x86/entry/32: Clean up syscall fast exit tests

Nikolay Borisov (6):
      x86: Introduce ia32_enabled()
      x86/entry: Rename ignore_sysret()
      x86/entry: Compile entry_SYSCALL32_ignore() unconditionally
      x86/elf: Make loading of 32bit processes depend on ia32_enabled()
      x86/entry: Make IA32 syscalls' availability depend on ia32_enabled()
      x86: Make IA32_EMULATION boot time configurable


 Documentation/admin-guide/kernel-parameters.txt |   6 ++
 arch/x86/Kconfig                                |   9 ++
 arch/x86/entry/common.c                         | 113 +++++++++++++++++-------
 arch/x86/entry/entry_32.S                       |   2 +-
 arch/x86/entry/entry_64.S                       |  72 +--------------
 arch/x86/entry/entry_64_compat.S                |  11 ++-
 arch/x86/include/asm/elf.h                      |   3 +-
 arch/x86/include/asm/ia32.h                     |  16 +++-
 arch/x86/include/asm/processor.h                |   2 +-
 arch/x86/include/asm/proto.h                    |   3 +
 arch/x86/include/asm/syscall.h                  |   6 +-
 arch/x86/kernel/cpu/common.c                    |  37 ++++----
 arch/x86/kernel/idt.c                           |   7 ++
 13 files changed, 155 insertions(+), 132 deletions(-)

             reply	other threads:[~2023-10-28 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-28 13:37 Ingo Molnar [this message]
2023-10-31  2:12 ` [GIT PULL] x86/entry changes for v6.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=ZT0OqhIh/7c9IOYU@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=ubizjak@gmail.com \
    /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.