From: Guenter Roeck <linux@roeck-us.net> To: Will Deacon <will@kernel.org> Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, Catalin Marinas <catalin.marinas@arm.com>, Jan Kara <jack@suse.cz>, Minchan Kim <minchan@kernel.org>, Andrew Morton <akpm@linux-foundation.org>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>, Linus Torvalds <torvalds@linux-foundation.org>, Vinayak Menon <vinmenon@codeaurora.org>, Hugh Dickins <hughd@google.com>, kernel-team@android.com Subject: Re: [PATCH v3 1/8] mm: Cleanup faultaround and finish_fault() codepaths Date: Wed, 10 Feb 2021 06:57:15 -0800 [thread overview] Message-ID: <2ed7aff4-3c07-364f-838b-7342625b12a1@roeck-us.net> (raw) In-Reply-To: <20210210114448.GA28682@willie-the-truck> On 2/10/21 3:44 AM, Will Deacon wrote: > On Tue, Feb 09, 2021 at 12:24:49PM -0800, Guenter Roeck wrote: >> On Thu, Jan 14, 2021 at 05:59:27PM +0000, Will Deacon wrote: >>> From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> >>> >>> alloc_set_pte() has two users with different requirements: in the >>> faultaround code, it called from an atomic context and PTE page table >>> has to be preallocated. finish_fault() can sleep and allocate page table >>> as needed. >>> >>> PTL locking rules are also strange, hard to follow and overkill for >>> finish_fault(). >>> >>> Let's untangle the mess. alloc_set_pte() has gone now. All locking is >>> explicit. >>> >>> The price is some code duplication to handle huge pages in faultaround >>> path, but it should be fine, having overall improvement in readability. >>> >>> Link: https://lore.kernel.org/r/20201229132819.najtavneutnf7ajp@box >>> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> >>> [will: s/from from/from/ in comment; spotted by willy] >>> Signed-off-by: Will Deacon <will@kernel.org> >>> --- >>> fs/xfs/xfs_file.c | 6 +- >>> include/linux/mm.h | 12 ++- >>> include/linux/pgtable.h | 11 +++ >>> mm/filemap.c | 177 ++++++++++++++++++++++++++--------- >>> mm/memory.c | 199 ++++++++++++---------------------------- >>> 5 files changed, 213 insertions(+), 192 deletions(-) >>> >> >> When building microblaze:mmu_defconfig: >> >> mm/filemap.c: In function 'filemap_map_pages': >> mm/filemap.c:3153:3: error: implicit declaration of function 'update_mmu_cache'; did you mean 'update_mmu_tlb'? >> >> Bisect log attached. > > Looks like a missing include. > Indeed. > Will > > --->8 > >>From 076f93117c067d5b6caab4773c6d6da130859cc4 Mon Sep 17 00:00:00 2001 > From: Will Deacon <will@kernel.org> > Date: Wed, 10 Feb 2021 11:15:11 +0000 > Subject: [PATCH] mm: filemap: Fix microblaze build failure with > 'mmu_defconfig' > > Commit f9ce0be71d1f ("mm: Cleanup faultaround and finish_fault() > codepaths") added a call to 'update_mmu_cache()' in mm/filemap.c, which > breaks the build for microblaze: > > | mm/filemap.c: In function 'filemap_map_pages': > | mm/filemap.c:3153:3: error: implicit declaration of function 'update_mmu_cache'; did you mean 'update_mmu_tlb'? > > Include asm/tlbflush.h in mm/filemap.c to make sure that the function > (or indeed, macro) is available. > > Reported-by: Guenter Roeck <linux@roeck-us.net> > Link: https://lore.kernel.org/r/20210209202449.GA104837@roeck-us.net > Signed-off-by: Will Deacon <will@kernel.org> Tested-by: Guenter Roeck <linux@roeck-us.net> > --- > mm/filemap.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/mm/filemap.c b/mm/filemap.c > index fb7a8d9b5603..2ca13227747b 100644 > --- a/mm/filemap.c > +++ b/mm/filemap.c > @@ -43,6 +43,7 @@ > #include <linux/ramfs.h> > #include <linux/page_idle.h> > #include <asm/pgalloc.h> > +#include <asm/tlbflush.h> > #include "internal.h" > > #define CREATE_TRACE_POINTS >
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net> To: Will Deacon <will@kernel.org> Cc: kernel-team@android.com, Jan Kara <jack@suse.cz>, Minchan Kim <minchan@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Hugh Dickins <hughd@google.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Vinayak Menon <vinmenon@codeaurora.org>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>, Andrew Morton <akpm@linux-foundation.org>, Linus Torvalds <torvalds@linux-foundation.org>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 1/8] mm: Cleanup faultaround and finish_fault() codepaths Date: Wed, 10 Feb 2021 06:57:15 -0800 [thread overview] Message-ID: <2ed7aff4-3c07-364f-838b-7342625b12a1@roeck-us.net> (raw) In-Reply-To: <20210210114448.GA28682@willie-the-truck> On 2/10/21 3:44 AM, Will Deacon wrote: > On Tue, Feb 09, 2021 at 12:24:49PM -0800, Guenter Roeck wrote: >> On Thu, Jan 14, 2021 at 05:59:27PM +0000, Will Deacon wrote: >>> From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> >>> >>> alloc_set_pte() has two users with different requirements: in the >>> faultaround code, it called from an atomic context and PTE page table >>> has to be preallocated. finish_fault() can sleep and allocate page table >>> as needed. >>> >>> PTL locking rules are also strange, hard to follow and overkill for >>> finish_fault(). >>> >>> Let's untangle the mess. alloc_set_pte() has gone now. All locking is >>> explicit. >>> >>> The price is some code duplication to handle huge pages in faultaround >>> path, but it should be fine, having overall improvement in readability. >>> >>> Link: https://lore.kernel.org/r/20201229132819.najtavneutnf7ajp@box >>> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> >>> [will: s/from from/from/ in comment; spotted by willy] >>> Signed-off-by: Will Deacon <will@kernel.org> >>> --- >>> fs/xfs/xfs_file.c | 6 +- >>> include/linux/mm.h | 12 ++- >>> include/linux/pgtable.h | 11 +++ >>> mm/filemap.c | 177 ++++++++++++++++++++++++++--------- >>> mm/memory.c | 199 ++++++++++++---------------------------- >>> 5 files changed, 213 insertions(+), 192 deletions(-) >>> >> >> When building microblaze:mmu_defconfig: >> >> mm/filemap.c: In function 'filemap_map_pages': >> mm/filemap.c:3153:3: error: implicit declaration of function 'update_mmu_cache'; did you mean 'update_mmu_tlb'? >> >> Bisect log attached. > > Looks like a missing include. > Indeed. > Will > > --->8 > >>From 076f93117c067d5b6caab4773c6d6da130859cc4 Mon Sep 17 00:00:00 2001 > From: Will Deacon <will@kernel.org> > Date: Wed, 10 Feb 2021 11:15:11 +0000 > Subject: [PATCH] mm: filemap: Fix microblaze build failure with > 'mmu_defconfig' > > Commit f9ce0be71d1f ("mm: Cleanup faultaround and finish_fault() > codepaths") added a call to 'update_mmu_cache()' in mm/filemap.c, which > breaks the build for microblaze: > > | mm/filemap.c: In function 'filemap_map_pages': > | mm/filemap.c:3153:3: error: implicit declaration of function 'update_mmu_cache'; did you mean 'update_mmu_tlb'? > > Include asm/tlbflush.h in mm/filemap.c to make sure that the function > (or indeed, macro) is available. > > Reported-by: Guenter Roeck <linux@roeck-us.net> > Link: https://lore.kernel.org/r/20210209202449.GA104837@roeck-us.net > Signed-off-by: Will Deacon <will@kernel.org> Tested-by: Guenter Roeck <linux@roeck-us.net> > --- > mm/filemap.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/mm/filemap.c b/mm/filemap.c > index fb7a8d9b5603..2ca13227747b 100644 > --- a/mm/filemap.c > +++ b/mm/filemap.c > @@ -43,6 +43,7 @@ > #include <linux/ramfs.h> > #include <linux/page_idle.h> > #include <asm/pgalloc.h> > +#include <asm/tlbflush.h> > #include "internal.h" > > #define CREATE_TRACE_POINTS > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 14:58 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 17:59 [PATCH v3 0/8] Create 'old' ptes for faultaround mappings on arm64 with hardware access flag Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-01-14 17:59 ` [PATCH v3 1/8] mm: Cleanup faultaround and finish_fault() codepaths Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-02-09 20:24 ` Guenter Roeck 2021-02-09 20:24 ` Guenter Roeck 2021-02-10 11:44 ` Will Deacon 2021-02-10 11:44 ` Will Deacon 2021-02-10 14:57 ` Guenter Roeck [this message] 2021-02-10 14:57 ` Guenter Roeck 2021-01-14 17:59 ` [PATCH v3 2/8] mm: Allow architectures to request 'old' entries when prefaulting Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-01-14 17:59 ` [PATCH v3 3/8] arm64: mm: Implement arch_wants_old_prefaulted_pte() Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-01-14 17:59 ` [RFC PATCH 4/8] mm: Separate fault info out of 'struct vm_fault' Will Deacon 2021-01-14 18:16 ` Linus Torvalds 2021-01-14 18:16 ` Linus Torvalds 2021-01-14 18:16 ` Linus Torvalds 2021-01-14 19:00 ` Will Deacon 2021-01-14 19:00 ` Will Deacon 2021-01-14 19:09 ` Linus Torvalds 2021-01-14 19:09 ` Linus Torvalds 2021-01-14 19:09 ` Linus Torvalds 2021-01-14 19:41 ` Will Deacon 2021-01-14 19:41 ` Will Deacon 2021-01-14 20:09 ` Nick Desaulniers 2021-01-14 20:09 ` Nick Desaulniers 2021-01-14 20:09 ` Nick Desaulniers 2021-01-14 21:11 ` Linus Torvalds 2021-01-14 21:11 ` Linus Torvalds 2021-01-14 21:11 ` Linus Torvalds 2021-01-15 9:23 ` Will Deacon 2021-01-15 9:23 ` Will Deacon 2021-01-15 21:32 ` Linus Torvalds 2021-01-15 21:32 ` Linus Torvalds 2021-01-15 21:32 ` Linus Torvalds 2021-01-20 0:00 ` Nick Desaulniers 2021-01-20 0:00 ` Nick Desaulniers 2021-01-20 0:00 ` Nick Desaulniers 2021-01-14 17:59 ` [RFC PATCH 5/8] mm: Pass 'address' to map to do_set_pte() and drop FAULT_FLAG_PREFAULT Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-01-14 18:17 ` Linus Torvalds 2021-01-14 18:17 ` Linus Torvalds 2021-01-14 18:17 ` Linus Torvalds 2021-01-15 10:24 ` Will Deacon 2021-01-15 10:24 ` Will Deacon 2021-01-14 17:59 ` [RFC PATCH 6/8] mm: Avoid modifying vmf.info.address in __collapse_huge_page_swapin() Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-01-14 17:59 ` [RFC PATCH 7/8] mm: Use static initialisers for 'info' field of 'struct vm_fault' Will Deacon 2021-01-14 17:59 ` Will Deacon 2021-01-14 17:59 ` [RFC PATCH 8/8] mm: Mark 'info' field of 'struct vm_fault' as 'const' Will Deacon 2021-01-14 17:59 ` Will Deacon
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=2ed7aff4-3c07-364f-838b-7342625b12a1@roeck-us.net \ --to=linux@roeck-us.net \ --cc=akpm@linux-foundation.org \ --cc=catalin.marinas@arm.com \ --cc=hughd@google.com \ --cc=jack@suse.cz \ --cc=kernel-team@android.com \ --cc=kirill.shutemov@linux.intel.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=minchan@kernel.org \ --cc=torvalds@linux-foundation.org \ --cc=vinmenon@codeaurora.org \ --cc=will@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.