From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: npiggin@gmail.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, akpm@linux-foundation.org, x86@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: [PATCH V5 0/5] NestMMU pte upgrade workaround for mprotect
Date: Tue, 29 Jan 2019 16:13:45 +0530 [thread overview]
Message-ID: <87va27agm6.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190116085035.29729-1-aneesh.kumar@linux.ibm.com>
Andrew,
How do you want to merge this? Michael Ellerman suggests this should go
via -mm tree.
-aneesh
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> We can upgrade pte access (R -> RW transition) via mprotect. We need
> to make sure we follow the recommended pte update sequence as outlined in
> commit bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang")
> for such updates. This patch series do that.
>
> Changes from V4:
> * Drop EXPORT_SYMBOL
>
> Changes from V3:
> * Build fix for x86
>
> Changes from V2:
> * Update commit message for patch 4
> * use radix tlb flush routines directly.
>
> Changes from V1:
> * Restrict ths only for R->RW upgrade. We don't need to do this for Autonuma
> * Restrict this only for radix translation mode.
>
>
> Aneesh Kumar K.V (5):
> mm: Update ptep_modify_prot_start/commit to take vm_area_struct as arg
> mm: update ptep_modify_prot_commit to take old pte value as arg
> arch/powerpc/mm: Nest MMU workaround for mprotect RW upgrade.
> mm/hugetlb: Add prot_modify_start/commit sequence for hugetlb update
> arch/powerpc/mm/hugetlb: NestMMU workaround for hugetlb mprotect RW
> upgrade
>
> arch/powerpc/include/asm/book3s/64/hugetlb.h | 12 ++++++++++
> arch/powerpc/include/asm/book3s/64/pgtable.h | 18 ++++++++++++++
> arch/powerpc/include/asm/book3s/64/radix.h | 4 ++++
> arch/powerpc/mm/hugetlbpage-hash64.c | 25 ++++++++++++++++++++
> arch/powerpc/mm/hugetlbpage-radix.c | 17 +++++++++++++
> arch/powerpc/mm/pgtable-book3s64.c | 25 ++++++++++++++++++++
> arch/powerpc/mm/pgtable-radix.c | 18 ++++++++++++++
> arch/s390/include/asm/pgtable.h | 5 ++--
> arch/s390/mm/pgtable.c | 8 ++++---
> arch/x86/include/asm/paravirt.h | 13 +++++-----
> arch/x86/include/asm/paravirt_types.h | 5 ++--
> arch/x86/xen/mmu.h | 4 ++--
> arch/x86/xen/mmu_pv.c | 8 +++----
> fs/proc/task_mmu.c | 8 ++++---
> include/asm-generic/pgtable.h | 18 +++++++-------
> include/linux/hugetlb.h | 20 ++++++++++++++++
> mm/hugetlb.c | 8 ++++---
> mm/memory.c | 8 +++----
> mm/mprotect.c | 6 ++---
> 19 files changed, 189 insertions(+), 41 deletions(-)
>
> --
> 2.20.1
next prev parent reply other threads:[~2019-01-29 10:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 8:50 [PATCH V5 0/5] NestMMU pte upgrade workaround for mprotect Aneesh Kumar K.V
2019-01-16 8:50 ` [PATCH V5 1/5] mm: Update ptep_modify_prot_start/commit to take vm_area_struct as arg Aneesh Kumar K.V
2019-01-30 10:33 ` Michael Ellerman
2019-01-16 8:50 ` [PATCH V5 2/5] mm: update ptep_modify_prot_commit to take old pte value " Aneesh Kumar K.V
2019-01-30 10:46 ` Michael Ellerman
2019-01-31 5:03 ` Aneesh Kumar K.V
2019-01-16 8:50 ` [PATCH V5 3/5] arch/powerpc/mm: Nest MMU workaround for mprotect RW upgrade Aneesh Kumar K.V
2019-01-30 10:52 ` Michael Ellerman
2019-01-31 5:07 ` Aneesh Kumar K.V
2019-01-16 8:50 ` [PATCH V5 4/5] mm/hugetlb: Add prot_modify_start/commit sequence for hugetlb update Aneesh Kumar K.V
2019-01-30 10:54 ` Michael Ellerman
2019-01-16 8:50 ` [PATCH V5 5/5] arch/powerpc/mm/hugetlb: NestMMU workaround for hugetlb mprotect RW upgrade Aneesh Kumar K.V
2019-01-30 11:01 ` Michael Ellerman
2019-01-29 10:43 ` Aneesh Kumar K.V [this message]
2019-01-29 18:29 ` [PATCH V5 0/5] NestMMU pte upgrade workaround for mprotect Andrew Morton
2019-02-26 23:37 ` Andrew Morton
2019-02-27 8:58 ` Aneesh Kumar K.V
2019-02-28 19:39 ` Andrew Morton
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=87va27agm6.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).