From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [git pull] x86 PAT changes
Date: Fri, 25 Apr 2008 18:12:37 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0804251808590.2813@woody.linux-foundation.org> (raw)
In-Reply-To: <481271F4.7060401@zytor.com>
On Fri, 25 Apr 2008, H. Peter Anvin wrote:
>
> The problem is that that can create cached/uncached aliases, which can cause
> some processors to lock up (especially AMD is known to have a lot of errata in
> this area.)
Umm.. I don't think you understand. Right now, NONPROMISC_DEVMEM doesn't
just disable mmap() on /dev/mem, it disables totally regular reads and
writes too. That seems pretty damn excessive.
If it was just mmap(), I don't think it would matter much. I don't think
we traditionally even supported mmap() on real RAM (because the page
counting would get confused), and that actually got supported only thanks
to VM changes that made it possible.
But read/write has always been supported, and shouldn't cause any
cached/uncached aliases!
Linus
next prev parent reply other threads:[~2008-04-26 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 22:56 Ingo Molnar
2008-04-25 23:43 ` Linus Torvalds
2008-04-26 0:06 ` H. Peter Anvin
2008-04-26 1:12 ` Linus Torvalds [this message]
2008-04-26 8:56 ` Ingo Molnar
2008-04-26 16:54 ` Pallipadi, Venkatesh
2008-04-26 17:15 ` Linus Torvalds
2008-04-26 18:32 ` Venki Pallipadi
2008-04-26 19:07 ` [patch] x86, PAT: disable /dev/mem mmap RAM with PAT Ingo Molnar
2008-04-26 9:57 ` [git pull] x86 PAT changes Ingo Molnar
2008-04-26 13:40 ` Gabriel C
2008-04-26 14:42 ` Ingo Molnar
2008-04-26 15:37 ` Gabriel C
2008-04-26 15:41 ` Ingo Molnar
2008-04-26 16:43 ` Linus Torvalds
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=alpine.LFD.1.10.0804251808590.2813@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®