[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091104032242.GC27772@yookeroo.seuss>
Date: Wed, 4 Nov 2009 14:22:42 +1100
From: David Gibson <david@...son.dropbear.id.au>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Hugh Dickins <hugh.dickins@...cali.co.uk>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
linuxppc-dev@...ts.ozlabs.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Filtering bits in set_pte_at()
On Tue, Nov 03, 2009 at 09:19:27AM +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2009-11-02 at 13:27 +0000, Hugh Dickins wrote:
> > On Sat, 31 Oct 2009, Benjamin Herrenschmidt wrote:
> >
> > > Hi folks !
> > >
> > > So I have a little problem on powerpc ... :-)
> >
> > Thanks a lot for running this by us.
>
> Heh, I though you may have been bored :-)
>
> > I've not looked to see if there are more such issues in arch/powerpc
> > itself, but those instances you mention are the only ones I managed
> > to find: uses of update_mmu_cache() and that hugetlb_cow() one.
>
> Right, that's all I spotted so far
>
> > The hugetlb_cow() one involves not set_pte_at() but set_huge_pte_at(),
> > so you'd want to change that too? And presumably set_pte_at_notify()?
> > It all seems a lot of tedium, when so very few places are interested
> > in the pte after they've set it.
>
> We need to change set_huge_pte_at() too. Currently, David fixed the
> problem in a local tree by making hugetlb_cow() re-read the PTE .
Well, actually I have another cleanup patch in the queue which makes
set_huge_pte_at() equal to set_pte_at() on powerpc, and I was using
that on the tree where this problem became apparent.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists