mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/urgent for v5.15-rc5
Date: Sun, 10 Oct 2021 10:56:06 +0200	[thread overview]
Message-ID: <YWKqpkLDl4Yd87z1@zn.tnic> (raw)

Hi Linus,

the last two weeks gathered in several x86/urgent fixes, please pull
them in.

Thx.

---

The following changes since commit 5816b3e6577eaa676ceb00a848f0fd65fe2adc29:

  Linux 5.15-rc3 (2021-09-26 14:08:19 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.15_rc5

for you to fetch changes up to d298b03506d3e161f7492c440babb0bfae35e650:

  x86/fpu: Restore the masking out of reserved MXCSR bits (2021-10-08 11:12:17 +0200)

----------------------------------------------------------------
- A FPU fix to properly handle invalid MXCSR values: 32-bit masks them
out due to histerical reasons and 64-bit kernels reject them

- A fix to clear X86_FEATURE_SMAP when support for is not config-enabled

- Three fixes correcting misspelled Kconfig symbols used in code

- Two resctrl object cleanup fixes

- Yet another attempt at fixing the neverending saga of botched x86
timers, this time because some incredibly smart hardware decides to turn
off the HPET timer in a low power state - who cares if the OS is relying
on it...

- Check the full return value range of an SEV VMGEXIT call to determine
whether it returned an error

----------------------------------------------------------------
Borislav Petkov (1):
      x86/fpu: Restore the masking out of reserved MXCSR bits

James Morse (2):
      x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails
      x86/resctrl: Fix kfree() of the wrong type in domain_add_cpu()

Lukas Bulwahn (3):
      x86/entry: Correct reference to intended CONFIG_64_BIT
      x86/platform/olpc: Correct ifdef symbol to intended CONFIG_OLPC_XO15_SCI
      x86/Kconfig: Correct reference to MWINCHIP3D

Thomas Gleixner (1):
      x86/hpet: Use another crystalball to evaluate HPET usability

Tom Lendacky (1):
      x86/sev: Return an error on a returned non-zero SW_EXITINFO1[31:0]

Vegard Nossum (1):
      x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n

 arch/x86/Kconfig                    |  2 +-
 arch/x86/include/asm/entry-common.h |  2 +-
 arch/x86/kernel/cpu/common.c        |  1 +
 arch/x86/kernel/cpu/resctrl/core.c  |  6 ++-
 arch/x86/kernel/early-quirks.c      |  6 ---
 arch/x86/kernel/fpu/signal.c        | 11 +++--
 arch/x86/kernel/hpet.c              | 81 +++++++++++++++++++++++++++++++++++++
 arch/x86/kernel/sev-shared.c        |  2 +
 arch/x86/platform/olpc/olpc.c       |  2 +-
 9 files changed, 99 insertions(+), 14 deletions(-)


-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

             reply	other threads:[~2021-10-10  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10  8:56 Borislav Petkov [this message]
2021-10-10 17:17 ` 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=YWKqpkLDl4Yd87z1@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®