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/mm for 6.9
Date: Mon, 11 Mar 2024 10:30:34 -0700 [thread overview]
Message-ID: <20240311173034.345007-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/mm changes for 6.9. The three changes are quite
diverse. No real common themes across them.
There is an extra merge in here from Ingo after 6.8-rc1. I believe
there were some early 6.8 bugs that were complicating testing x86/mm
and the merge made thing easier.
--
The following changes since commit ecb1b8288dc7ccbdcb3b9df005fa1c0e0c0388a7:
Merge tag 'net-6.8-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2024-01-25 10:58:35 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_mm_for_6.9
for you to fetch changes up to 82ace185017fbbe48342bf7d8a9fd795f9c711cd:
x86/mm/cpa: Warn for set_memory_XXcrypted() VMM fails (2024-02-22 14:25:41 -0800)
----------------------------------------------------------------
* Add a warning when memory encryption conversions fail. These
operations require VMM cooperation, even in CoCo environments
where the VMM is untrusted. While it's _possible_ that memory
pressure could trigger the new warning, the odds are that a
guest would only see this from an attacking VMM.
* Simplify page fault code by re-enabling interrupts unconditionally
* Avoid truncation issues when pfns are passed in to
pfn_to_kaddr() with small (<64-bit) types.
----------------------------------------------------------------
Ingo Molnar (1):
Merge branch 'linus' into x86/mm, to refresh the branch and pick up fixes
Linus Torvalds (1):
x86/mm: Get rid of conditional IF flag handling in page fault path
Michael Roth (1):
x86/mm: Ensure input to pfn_to_kaddr() is treated as a 64-bit type
Rick Edgecombe (1):
x86/mm/cpa: Warn for set_memory_XXcrypted() VMM fails
arch/x86/include/asm/page.h | 6 +++++-
arch/x86/mm/fault.c | 27 ++++++++++++++-------------
arch/x86/mm/pat/set_memory.c | 19 +++++++++++++------
3 files changed, 32 insertions(+), 20 deletions(-)
next reply other threads:[~2024-03-11 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 17:30 Dave Hansen [this message]
2024-03-12 3:32 ` [GIT PULL] x86/mm for 6.9 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=20240311173034.345007-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