linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Will Deacon <will.deacon@arm.com>
Cc: Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hillf Danton <dhillf@gmail.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: hugetlb: flush dcache before returning zeroed huge page to userspace
Date: Thu, 12 Jul 2012 13:16:59 +0200	[thread overview]
Message-ID: <20120712111659.GF21013@tiehlicka.suse.cz> (raw)
In-Reply-To: <20120711174802.GG13498@mudshark.cambridge.arm.com>

On Wed 11-07-12 18:48:02, Will Deacon wrote:
> On Tue, Jul 10, 2012 at 11:42:34AM +0100, Will Deacon wrote:
> > On Tue, Jul 10, 2012 at 10:45:13AM +0100, Will Deacon wrote:
> > > On Tue, Jul 10, 2012 at 12:57:14AM +0100, Hugh Dickins wrote:
> > > > If I start to grep the architectures for non-empty flush_dcache_page(),
> > > > I soon find things in arch/arm such as v4_mc_copy_user_highpage() doing
> > > > if (!test_and_set_bit(PG_dcache_clean,)) __flush_dcache_page() - where
> > > > the naming suggests that I'm right, it's the architecture's responsibility
> > > > to arrange whatever flushing is needed in its copy and clear page functions.
> 
> [...]
> 
> > Ok, so this is exactly the problem. The hugetlb allocator uses its own
> > pool of huge pages, so free_huge_page followed by a later alloc_huge_page
> > will give you something where the page flags of the compound head do not
> > guarantee that PG_arch_1 is clear.
> 
> Just to confirm, the following quick hack at least results in the correct
> flushing for me (on ARM):
> 
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index e198831..7a7c9d3 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1141,6 +1141,7 @@ static struct page *alloc_huge_page(struct vm_area_struct *vma,
>         }
>  
>         set_page_private(page, (unsigned long)spool);
> +       clear_bit(PG_arch_1, &page->flags);
>  
>         vma_commit_reservation(h, vma, addr);
>  
> 
> 
> The question is whether we should tidy that up for the core code or get
> architectures to clear the bit in arch_make_huge_pte (which also seems to
> work).

This should go into arch specific code IMO. Even the page flag name
suggests this shouldn't be in the base code.

> 
> Will

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@suse.cz>
To: Will Deacon <will.deacon@arm.com>
Cc: Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hillf Danton <dhillf@gmail.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: hugetlb: flush dcache before returning zeroed huge page to userspace
Date: Thu, 12 Jul 2012 13:16:59 +0200	[thread overview]
Message-ID: <20120712111659.GF21013@tiehlicka.suse.cz> (raw)
Message-ID: <20120712111659.eR-WUhsQwHLiC0P7Zq3hGvdDLUBwn5dMCMUEm9LolsM@z> (raw)
In-Reply-To: <20120711174802.GG13498@mudshark.cambridge.arm.com>

On Wed 11-07-12 18:48:02, Will Deacon wrote:
> On Tue, Jul 10, 2012 at 11:42:34AM +0100, Will Deacon wrote:
> > On Tue, Jul 10, 2012 at 10:45:13AM +0100, Will Deacon wrote:
> > > On Tue, Jul 10, 2012 at 12:57:14AM +0100, Hugh Dickins wrote:
> > > > If I start to grep the architectures for non-empty flush_dcache_page(),
> > > > I soon find things in arch/arm such as v4_mc_copy_user_highpage() doing
> > > > if (!test_and_set_bit(PG_dcache_clean,)) __flush_dcache_page() - where
> > > > the naming suggests that I'm right, it's the architecture's responsibility
> > > > to arrange whatever flushing is needed in its copy and clear page functions.
> 
> [...]
> 
> > Ok, so this is exactly the problem. The hugetlb allocator uses its own
> > pool of huge pages, so free_huge_page followed by a later alloc_huge_page
> > will give you something where the page flags of the compound head do not
> > guarantee that PG_arch_1 is clear.
> 
> Just to confirm, the following quick hack at least results in the correct
> flushing for me (on ARM):
> 
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index e198831..7a7c9d3 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1141,6 +1141,7 @@ static struct page *alloc_huge_page(struct vm_area_struct *vma,
>         }
>  
>         set_page_private(page, (unsigned long)spool);
> +       clear_bit(PG_arch_1, &page->flags);
>  
>         vma_commit_reservation(h, vma, addr);
>  
> 
> 
> The question is whether we should tidy that up for the core code or get
> architectures to clear the bit in arch_make_huge_pte (which also seems to
> work).

This should go into arch specific code IMO. Even the page flag name
suggests this shouldn't be in the base code.

> 
> Will

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

  parent reply	other threads:[~2012-07-12 11:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1341412376-6272-1-git-send-email-will.deacon@arm.com>
     [not found] ` <20120709122523.GC4627@tiehlicka.suse.cz>
     [not found]   ` <20120709141324.GK7315@mudshark.cambridge.arm.com>
2012-07-09 23:57     ` [PATCH] mm: hugetlb: flush dcache before returning zeroed huge page to userspace Hugh Dickins
2012-07-10  9:45       ` Will Deacon
2012-07-10  9:45         ` Will Deacon
2012-07-10 10:42         ` Will Deacon
2012-07-10 10:42           ` Will Deacon
2012-07-11 17:48           ` Will Deacon
2012-07-11 17:48             ` Will Deacon
2012-07-12 11:16             ` Michal Hocko [this message]
2012-07-12 11:16               ` Michal Hocko
2012-07-12 11:26               ` James Bottomley
2012-07-12 11:26               ` Will Deacon
2012-07-12 11:26                 ` Will Deacon
2012-07-12 11:57                 ` Michal Hocko
2012-07-12 11:57                   ` Michal Hocko
2012-08-07 16:03                   ` Will Deacon
2012-08-07 16:03                     ` Will Deacon
2012-08-08 16:26                     ` Michal Hocko
2012-08-08 16:26                       ` Michal Hocko
2012-08-16 16:09                       ` Will Deacon
2012-08-16 16:09                         ` Will Deacon
2012-08-16 17:25                         ` Michal Hocko
2012-08-16 17:25                           ` Michal Hocko
2012-08-16 17:34                           ` Will Deacon
2012-08-16 17:34                             ` Will Deacon
2012-08-16 18:06                             ` Michal Hocko
2012-08-16 18:19                               ` Will Deacon
2012-08-16 18:20                         ` Michal Hocko
2012-08-16 18:32                           ` Will Deacon
2012-08-16 18:32                             ` 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=20120712111659.GF21013@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=dhillf@gmail.com \
    --cc=hughd@google.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=will.deacon@arm.com \
    /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).