From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-mm-sig] [PATCH] ARM: LPAE: fix access flag setup in mem_type_table
Date: Tue, 15 May 2012 22:51:27 +0200 [thread overview]
Message-ID: <4FB2C1CF.2030208@samsung.com> (raw)
In-Reply-To: <20120515122215.GK10453@n2100.arm.linux.org.uk>
Hello,
On 5/15/2012 2:22 PM, Russell King - ARM Linux wrote:
> On Mon, May 14, 2012 at 01:54:57PM -0400, Vitaly Andrianov wrote:
>> A zero value for prot_sect in the memory types table implies that
>> section mappings should never be created for the memory type in question.
>> This is checked for in alloc_init_section().
>>
>> With LPAE, we set a bit to mask access flag faults for kernel mappings.
>> This breaks the aforementioned (!prot_sect) check in alloc_init_section().
>>
>> This patch fixes this bug by first checking for a non-zero
>> prot_sect before setting the PMD_SECT_AF flag.
>>
>> Signed-off-by: Vitaly Andrianov<vitalya@ti.com>
>>
>> Acked-by: Catalin Marinas<catalin.marinas@arm.com>
>
> Please put this in the patch system. No blank line is needed between
> s-off-by and acked-by.
This patch fixes the issue introduced by adding CMA to ARM architecture
which I've pushed for testing to linux-next. I've added it to my
for-next-cma branch:
http://git.linaro.org/gitweb?p=people/mszyprowski/linux-dma-mapping.git;a=shortlog;h=refs/heads/for-next-cma
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-05-15 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 17:54 [PATCH] ARM: LPAE: fix access flag setup in mem_type_table Vitaly Andrianov
2012-05-15 12:22 ` Russell King - ARM Linux
2012-05-15 20:51 ` Marek Szyprowski [this message]
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=4FB2C1CF.2030208@samsung.com \
--to=m.szyprowski@samsung.com \
--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 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.