From: Arjan van de Ven <arjan@infradead.org>
To: Felix Rubinstein <felixru@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/mem implementation
Date: Sun, 17 Jan 2010 09:40:43 -0800 [thread overview]
Message-ID: <20100117094043.0483ee1a@infradead.org> (raw)
In-Reply-To: <af0693f01001170847r49083075hc538a42b6bcd65ab@mail.gmail.com>
On Sun, 17 Jan 2010 18:47:10 +0200
Felix Rubinstein <felixru@gmail.com> wrote:
> I see the motivation to limit the access to DRAM from root account
> CONFIG_STRICT_DEVMEM by mmap'ing /dev/[k]mem but it's easily overruled
> by simple char driver and implementing mmap of it's own totally
> bypassing all limitations.
>
> What do you think about it guy?
> Appreciate it.
the reason PAT bans parts of /dev/mem is simple: it is illegal to have
mapping aliases (different cachability) for the same physical page.
Normal kernel APIs take care of this for the normal case, but /dev/mem
would be a back door into that.
This is a hardware imposed requirement, and violating the rule can have
really nasty consequences... hence the PAT code just not allowing it.
If you feel that you have a valid use case where you really want do
muck with such memory, it might be a good idea to explain that
usecase....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2010-01-17 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 16:47 Felix Rubinstein
2010-01-17 17:40 ` Arjan van de Ven [this message]
2010-01-18 10:22 ` Andi Kleen
2010-01-18 12:18 ` Felix Rubinstein
2010-01-18 15:16 ` Arjan van de Ven
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=20100117094043.0483ee1a@infradead.org \
--to=arjan@infradead.org \
--cc=felixru@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®