From: "H. Peter Anvin" <hpa@zytor.com>
To: Len Brown <lenb@kernel.org>
Cc: Jack Steiner <steiner@sgi.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
tony.luck@gmail.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, gbeshers@sgi.com
Subject: Re: [PATCH] - Mapping ACPI tables as CACHED
Date: Tue, 14 Dec 2010 22:17:29 -0800 [thread overview]
Message-ID: <4D085D79.4010308@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1012142317450.4878@x980>
On 12/14/2010 08:35 PM, Len Brown wrote:
>
> I'm not sure the concept of checking against E820
> is better than simply calling ioremap_cache() always.
>
I don't think it is. On most systems, non-RAM will be forced uncachable
by the MTRRs anyway, and if we find systems which have problems, we
should be doing this forcing in the PAT subsystem, not in ACPI.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-12-15 6:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 22:09 [PATCH] - Mapping ACPI tables as CACHED Jack Steiner
2010-12-14 22:58 ` H. Peter Anvin
2010-12-14 23:22 ` Len Brown
2010-12-15 0:26 ` H. Peter Anvin
2010-12-15 2:27 ` Jack Steiner
2010-12-15 4:17 ` H. Peter Anvin
2010-12-15 0:04 ` Len Brown
2010-12-15 1:18 ` H. Peter Anvin
2010-12-15 2:40 ` Len Brown
2010-12-15 2:41 ` Jack Steiner
2010-12-15 4:03 ` Len Brown
2010-12-15 4:35 ` Len Brown
2010-12-15 6:17 ` H. Peter Anvin [this message]
2010-12-15 6:17 ` Milton Miller
2010-12-15 6:29 ` H. Peter Anvin
2010-12-15 16:46 ` Jack Steiner
2010-12-15 21:16 ` Len Brown
2010-12-15 22:18 ` H. Peter Anvin
2010-12-17 2:54 ` Len Brown
2010-12-17 8:08 ` [PATCH] ACPI: use ioremap_cache() Len Brown
2010-12-27 19:42 ` Tony Luck
2010-12-27 20:12 ` H. Peter Anvin
2010-12-28 3:21 ` Shaohua Li
2010-12-28 3:35 ` H. Peter Anvin
2010-12-28 5:02 ` Shaohua Li
2010-12-28 20:12 ` H. Peter Anvin
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=4D085D79.4010308@zytor.com \
--to=hpa@zytor.com \
--cc=gbeshers@sgi.com \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tony.luck@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.