From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Haren Myneni <haren@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH 0/3] powerpc/64s: Restrict NMMU workarounds
Date: Wed, 25 May 2022 12:23:55 +1000 [thread overview]
Message-ID: <20220525022358.780745-1-npiggin@gmail.com> (raw)
POWER10 doesn't require the two Nest MMU workarounds according to the
workbook. Also remove the last vestige of the spurious fault flushing
for NMMU which shouldn't have been required anyway.
Thanks,
Nick
Nicholas Piggin (3):
powerpc/64s: POWER10 nest MMU does not require flush escalation
workaround
powerpc/64s: POWER10 nest MMU can upgrade PTE access authority without
TLB flush
powerpc/64s: Remove spurious fault flushing for NMMU
arch/powerpc/include/asm/book3s/64/tlbflush.h | 28 +++++++++++++--
arch/powerpc/mm/book3s64/radix_hugetlbpage.c | 10 +++---
arch/powerpc/mm/book3s64/radix_pgtable.c | 35 ++++++++++++-------
arch/powerpc/mm/book3s64/radix_tlb.c | 14 ++++++--
4 files changed, 64 insertions(+), 23 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-25 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 2:23 Nicholas Piggin [this message]
2022-05-25 2:23 ` [PATCH 1/3] powerpc/64s: POWER10 nest MMU does not require flush escalation workaround Nicholas Piggin
2022-05-25 2:23 ` [PATCH 2/3] powerpc/64s: POWER10 nest MMU can upgrade PTE access authority without TLB flush Nicholas Piggin
2022-05-25 2:23 ` [PATCH 3/3] powerpc/64s: Remove spurious fault flushing for NMMU Nicholas Piggin
2022-07-29 13:02 ` [PATCH 0/3] powerpc/64s: Restrict NMMU workarounds Michael Ellerman
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=20220525022358.780745-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=haren@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).