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/mm for v6.0
Date: Mon, 1 Aug 2022 11:21:47 +0200 [thread overview]
Message-ID: <YuebK2LYy6INgX5E@zn.tnic> (raw)
Hi Linus,
please pull the small x86/mm lineup for 6.0.
Thx.
---
The following changes since commit e19d11267f0e6c8aff2d15d2dfed12365b4c9184:
x86/mm: Use PAGE_ALIGNED(x) instead of IS_ALIGNED(x, PAGE_SIZE) (2022-05-27 12:19:56 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_mm_for_v6.0_rc1
for you to fetch changes up to 8f1d56f64f8d6b80dea2d1978d10071132a695c5:
x86/mm/tlb: Ignore f->new_tlb_gen when zero (2022-07-19 09:04:52 -0700)
----------------------------------------------------------------
- Rename a PKRU macro to make more sense when reading the code
- Update pkeys documentation
- Avoid reading contended mm's TLB generation var if not absolutely
necessary along with fixing a case where arch_tlbbatch_flush() doesn't
adhere to the generation scheme and thus violates the conditions for the
above avoidance.
----------------------------------------------------------------
Ira Weiny (2):
Documentation/protection-keys: Clean up documentation for User Space pkeys
x86/pkeys: Clarify PKRU_AD_KEY macro
Nadav Amit (2):
x86/mm/tlb: Avoid reading mm_tlb_gen when possible
x86/mm/tlb: Ignore f->new_tlb_gen when zero
Documentation/core-api/protection-keys.rst | 44 ++++++++++++++----------------
arch/x86/include/asm/tlbflush.h | 1 +
arch/x86/mm/pkeys.c | 15 ++++++----
arch/x86/mm/tlb.c | 31 +++++++++++++++++++--
4 files changed, 59 insertions(+), 32 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-08-01 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 9:21 Borislav Petkov [this message]
2022-08-01 17:27 ` 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=YuebK2LYy6INgX5E@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®