From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 071/149] ARM: 6166/1: Proper prefetch abort handling on pre-ARMv6
Date: Wed, 7 Jul 2010 23:34:18 +0100 [thread overview]
Message-ID: <20100707223417.GA22673@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100707085601.GA18732@shutemov.name>
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.
> 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.
next prev parent reply other threads:[~2010-07-07 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100701175144.GA2116@kroah.com>
[not found] ` <20100701173212.785441106@clark.site>
[not found] ` <20100701221420.GA10481@shutemov.name>
[not found] ` <20100701221728.GA12187@suse.de>
[not found] ` <20100701222541.GB10481@shutemov.name>
[not found] ` <20100701224837.GA27389@flint.arm.linux.org.uk>
[not found] ` <20100701225911.GC10481@shutemov.name>
[not found] ` <20100701231207.GB27389@flint.arm.linux.org.uk>
[not found] ` <20100706130618.GA14177@shutemov.name>
[not found] ` <20100706225815.GA21834@flint.arm.linux.org.uk>
2010-07-07 8:56 ` [patch 071/149] ARM: 6166/1: Proper prefetch abort handling on pre-ARMv6 Kirill A. Shutemov
2010-07-07 22:34 ` Russell King - ARM Linux [this message]
2010-07-08 11:31 ` Kirill A. Shutemov
2010-07-12 22:08 ` Kirill A. Shutemov
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=20100707223417.GA22673@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).