[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100708113122.GA23854@shutemov.name>
Date: Thu, 8 Jul 2010 14:31:22 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: linux-kernel@...r.kernel.org, alan@...rguk.ukuu.org.uk,
Anfei Zhou <anfei.zhou@...il.com>,
Alexander Shishkin <virtuoso@...nd.org>,
Siarhei Siamashka <siarhei.siamashka@...ia.com>,
linux-arm-kernel@...ts.infradead.org, linux-mm@...ck.org
Subject: Re: [patch 071/149] ARM: 6166/1: Proper prefetch abort handling on
pre-ARMv6
On Wed, Jul 07, 2010 at 11:34:18PM +0100, Russell King - ARM Linux wrote:
> On Wed, Jul 07, 2010 at 11:56:01AM +0300, Kirill A. Shutemov wrote:
> > But it seems that the problem is more global. Potentially, any of
> > pmd_none() check may produce false results. I don't see an easy way to fix
> > it.
>
> It isn't. We normally guarantee that we always fill on both L1 entries.
> The only exception is for the mappings specified via create_mapping()
> which is used for the static platform mappings.
Why do not to change create_mapping() to follow the same rules?
I mean, create sections only if it asked for 2*SECTION_SIZE with
appropriate alignment. It reduces number of section mappings, but,
probably, will be a bit cleaner and less error-prune.
> > Does Linux VM still expect one PTE table per page?
>
> Yes, and as far as I can see probably always will. Hence why we need
> to put two L1 entries in one page and lie to the kernel about the sizes
> of the hardware entries.
Another option is leave half of page with PTE table free. Is it very bad
idea?
How other architectures handle it? Or only on ARM PTL table size is less
than page size?
--
Kirill A. Shutemov
--
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