From: ierton@gmail.com (Sergey Mironov)
To: linux-arm-kernel@lists.infradead.org
Subject: RAM bank with features
Date: Fri, 28 Jan 2011 17:28:29 +0300 [thread overview]
Message-ID: <AANLkTimDFdP7O3h9Zrx2gacqaBS=8TVfpeZP5cFX+T2e@mail.gmail.com> (raw)
Hello, community. I am porting Linux to arm1176-based SoC. Our system
has 2 RAM banks. First one (EM0) is quite common, but another (EM1)
has some "features" :
1) Critical one. There are devices that can't use DMA buffers outside EM1.
2) CPU can read and write to it, but can't execute instructions.
What is the finest way of implementing those restrictions? I thought
about defining custom memory zone, but I can't see how to link zones
with platform_device.dev.dma_mask.
Also, is it possible to allocate user pages from EM1 but prevent users
from executing code from them? Say, tell allocator to mark them with
L_PTE_* flag?
Thanks,
Sergey.
next reply other threads:[~2011-01-28 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 14:28 Sergey Mironov [this message]
2011-01-28 14:46 ` RAM bank with features Russell King - ARM Linux
2011-01-29 15:16 ` Sergey Mironov
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='AANLkTimDFdP7O3h9Zrx2gacqaBS=8TVfpeZP5cFX+T2e@mail.gmail.com' \
--to=ierton@gmail.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).