From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: change_page_attr() implementation for ARM?
Date: Thu, 17 Oct 2013 11:13:26 +0100 [thread overview]
Message-ID: <20131017101325.GD23462@arm.com> (raw)
In-Reply-To: <20131017.080523.1821831578701162178.hdoyu@nvidia.com>
On Thu, Oct 17, 2013 at 06:05:23AM +0100, Hiroshi Doyu wrote:
> I found a bit old discussion[1] about CPA support on ARM32(Cortex-A9).
>
> It seesm that CPA API on ARM wasn't possible because maintaining
> multiple pagetables under SMP is difficult. Instead currently we are
> using precallocated memory via DMA API.
>
> Is this situation still same for Cortex-A15 and ARM64? If the
> mismatched aliasing problem doesn't happen, is CPA API feasible?
On ARMv7+LPAE and AArch64 we use separate TTBR1 for the kernel (linear)
mapping so in theory you could implement change_page_attr(). The
mismatched aliases restriction still exists but it is clarified on what
is and isn't allowed (so you can have Normal non-cacheable and Normal
cacheable aliases, as long as you take care of removing any dirty cache
lines that could potentially corrupt your data). The DMA API already
takes care of this.
My (other) problem with change_page_attr() is that its not a standard
in-kernel API. Powerpc and s390 implement change_page_attr() but with
different arguments while x86 has change_page_attr_(set|clear).
So, is the DMA API not enough for what you need?
--
Catalin
next prev parent reply other threads:[~2013-10-17 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 5:05 change_page_attr() implementation for ARM? Hiroshi Doyu
2013-10-17 10:13 ` Catalin Marinas [this message]
2013-10-17 10:28 ` Hiroshi Doyu
2013-11-12 13:45 ` Hiroshi Doyu
2013-11-14 15:41 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2011-09-21 22:10 Vinod Rex
2011-09-23 9:04 ` Catalin Marinas
2011-10-13 2:27 ` Krishna Reddy
2011-10-13 8:49 ` Russell King - ARM Linux
2011-10-13 8:59 ` Catalin Marinas
2011-10-13 8:52 ` Catalin Marinas
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=20131017101325.GD23462@arm.com \
--to=catalin.marinas@arm.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 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).