archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <>
To: Linus Torvalds <>
Cc: x86-ml <>, lkml <>
Subject: [GIT PULL] x86/cpu for 6.1
Date: Tue, 4 Oct 2022 10:50:13 +0200	[thread overview]
Message-ID: <YzvzxYCBAPX47PTf@zn.tnic> (raw)

Hi Linus,

please pull the x86/cpu lineup for 6.1.



The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

  git:// tags/x86_cpu_for_v6.1_rc1

for you to fetch changes up to c926087eb38520b268515ae1a842db6db62554cc:

  x86/mm: Print likely CPU at segfault time (2022-08-24 12:48:05 +0200)

- Print the CPU number at segfault time. The number printed is not
  always accurate (preemption is enabled at that time) but the print string
  contains "likely" and after a lot of back'n'forth on this, this was the
  consensus that was reached. See thread starting at:

- After a *lot* of testing and polishing, finally the clear_user()
  improvements to inline REP; STOSB by default

Borislav Petkov (1):
      x86/clear_user: Make it faster

Rik van Riel (1):
      x86/mm: Print likely CPU at segfault time

 arch/x86/include/asm/uaccess.h    |   5 +-
 arch/x86/include/asm/uaccess_64.h |  45 +++++++++++++
 arch/x86/lib/clear_page_64.S      | 138 ++++++++++++++++++++++++++++++++++++++
 arch/x86/lib/usercopy_64.c        |  40 -----------
 arch/x86/mm/fault.c               |  10 +++
 tools/objtool/check.c             |   3 +
 6 files changed, 198 insertions(+), 43 deletions(-)


SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

             reply	other threads:[~2022-10-04  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  8:50 Borislav Petkov [this message]
2022-10-04 17:34 ` [GIT PULL] x86/cpu for 6.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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YzvzxYCBAPX47PTf@zn.tnic \ \ \ \ \

* 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).