From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michal Svoboda <michal.svoboda@agents.felk.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig: Make config Filter access to /dev/mem default y
Date: Thu, 15 Apr 2010 14:59:40 +0100 [thread overview]
Message-ID: <20100415145940.243723b7@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100415134152.GK21894@myhost.felk.cvut.cz>
On Thu, 15 Apr 2010 15:41:53 +0200
Michal Svoboda <michal.svoboda@agents.felk.cvut.cz> wrote:
> Jiri Kosina wrote:
> > Access to /dev/mem being filtered in PAT obviously applies only to x86.
> >
> > Architectures which don't do such filtering in their respective
> > phys_mem_access_prot_allowed() still need this option.
>
> So why not use it for all archs uniformly? Is PAT filtering better in
> some ways?
PAT is an x86 specific hardware feature. The x86 processors can set per
page caching properties as with some other CPU designs. In the x86 case
all references to the page must have the same cache settings so the PAT
implementation has to filter /dev/mem access to avoid machine check
errors.
It's not implemented as a security feature, its a side effect of the
hardware requirements on that CPU range.
Alan
next prev parent reply other threads:[~2010-04-15 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 2:52 wzt.wzt
2010-04-15 6:12 ` Xiaotian Feng
2010-04-15 6:17 ` wzt wzt
2010-04-15 6:28 ` Xiaotian Feng
2010-04-15 6:39 ` wzt wzt
2010-04-15 7:12 ` Xiaotian Feng
2010-04-15 7:37 ` wzt wzt
2010-04-15 6:36 ` Michal Svoboda
2010-04-15 10:43 ` Jiri Kosina
2010-04-15 13:41 ` Michal Svoboda
2010-04-15 13:59 ` Alan Cox [this message]
2010-04-15 11:00 ` Alan Cox
2010-04-15 18:03 ` Pavel Machek
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=20100415145940.243723b7@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.svoboda@agents.felk.cvut.cz \
/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®