From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
venkatesh.pallipadi@intel.com, linux-kernel@vger.kernel.org,
tim@scalemp.com, shai@scalex86.org
Subject: Re: [patch] x86: Fix /dev/mem mmap breakage when PAT is disabled
Date: Thu, 30 Oct 2008 14:54:56 -0700 [thread overview]
Message-ID: <20081030215455.GC6583@localdomain> (raw)
In-Reply-To: <20081030142949.75df90cc@infradead.org>
On Thu, Oct 30, 2008 at 02:29:49PM -0700, Arjan van de Ven wrote:
>On Thu, 30 Oct 2008 14:21:21 -0700
>Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
>
>> On Thu, Oct 30, 2008 at 01:21:03PM -0700, Arjan van de Ven wrote:
>> >On Wed, 29 Oct 2008 19:02:03 -0700
>> >Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
>> >
>> >well... technically the aliases are bad without PAT as well...
>> >
>>
>> Hmm! Well, you mean if mtrr is used to change attributes?
>
>you can also set uncached in the pagetables, like via ioremap_uncached
>and other ways.
>
>and /dev/mem may or may not imply cached/uncached, depending on the
>open flags.
>
>On memory... what would that mean?
>
Well, I am not denying that an incorrectly written userspace program could cause
cache aliasing/crash the system I am not arguing for or against this
argument at all.
However, there is what seems like an unintended change in behavior from
2.6.25 to 2.6.26 when CONFIG_STRICT_DEVMEM is disabled and PAT is disabled,
which is a bug, and this patch fixes it that's all. If this was intentional,
then I don't see the reason for having CONFIG_STRICT_DEVMEM!!
prev parent reply other threads:[~2008-10-30 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 2:02 [patch] x86: Fix /dev/mem mmap breakage when PAT is disabled Ravikiran G Thirumalai
2008-10-30 18:29 ` Ingo Molnar
2008-10-30 20:59 ` Ravikiran G Thirumalai
2008-10-30 22:55 ` Ingo Molnar
2008-10-30 20:21 ` Arjan van de Ven
2008-10-30 21:21 ` Ravikiran G Thirumalai
2008-10-30 21:29 ` Arjan van de Ven
2008-10-30 21:54 ` Ravikiran G Thirumalai [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=20081030215455.GC6583@localdomain \
--to=kiran@scalex86.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shai@scalex86.org \
--cc=tim@scalemp.com \
--cc=venkatesh.pallipadi@intel.com \
/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