The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/urgent for 6.4-rc4
Date: Mon, 22 May 2023 16:15:48 -0700	[thread overview]
Message-ID: <20230522231548.1511061-1-dave.hansen@linux.intel.com> (raw)

Hi Linus,

Please pull a single x86/urgent change for 6.4-rc4.  This works around
and issue where the INVLPG instruction may miss invalidating kernel
TLB entries.  I do expect an eventual microcode fix for this.  When
the microcode version numbers are known, we can circle back around and
add them the model table to disable this workaround.

--

The following changes since commit 7d8accfaa0ab65e4282c8e58950f7d688342cd86:

  hwmon: (k10temp) Add PCI ID for family 19, model 78h (2023-05-08 11:36:19 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_6.4-rc4

for you to fetch changes up to ce0b15d11ad837fbacc5356941712218e38a0a83:

  x86/mm: Avoid incomplete Global INVLPG flushes (2023-05-17 08:55:02 -0700)

----------------------------------------------------------------
Work around a TLB invalidation issue in recent hybrid CPUs

----------------------------------------------------------------
Dave Hansen (1):
      x86/mm: Avoid incomplete Global INVLPG flushes

 arch/x86/mm/init.c | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

             reply	other threads:[~2023-05-23  0:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 23:15 Dave Hansen [this message]
2023-05-23  0:30 ` [GIT PULL] x86/urgent for 6.4-rc4 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-05-28  7:52 [GIT pull] irq/urgent " Thomas Gleixner
2023-05-28  7:53 ` [GIT pull] x86/urgent " Thomas Gleixner
2023-05-28 11:46   ` 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=20230522231548.1511061-1-dave.hansen@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --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