From: "H. Peter Anvin" <hpa@zytor.com>
To: Jack Steiner <steiner@sgi.com>
Cc: hmh@hmh.eng.br, mingo@elte.hu, tglx@linutronix.de,
lenb@kernel.org, tony.luck@gmail.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC - V2] - Mapping ACPI tables as CACHED
Date: Thu, 26 Aug 2010 11:08:02 -0700 [thread overview]
Message-ID: <4C76AD82.2030105@zytor.com> (raw)
In-Reply-To: <20100826171704.GA21584@sgi.com>
On 08/26/2010 10:17 AM, Jack Steiner wrote:
> Map ACPI tables as WB on x86_64. No substantive changes to IA64.
>
>
> Signed-off-by: Jack Steiner <steiner@sgi.com>
>
> ---
> V2 - Change the patch to unconditionally map ACPI tables as WB on x86_64.
> I'm still some paranoid about this because of the potential imapct on
> some platforms with weird BIOSs. However, note that on EFI-enabled
> systems (like UV), the ACPI tables are already mapped as WB memory.
> This is done in the EFI function efi_enter_virtual_mode().
> The ACPI code in acpi_os_map_memory() is not currently aware of the
> EFI mapping & currently maps the memory as UC. This seems like a bug.
>
I really think that it's all a consequence of the fact that ioremap()
became implicitly UC when we added PAT support (being the more
conservative choice.)
Len, want to take this one or should I?
-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-08-26 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 15:22 [RFC] - Mapping ACPI tables as CACHED Jack Steiner
2010-07-22 15:52 ` Len Brown
2010-07-23 16:38 ` Jack Steiner
2010-07-23 1:46 ` ykzhao
2010-07-23 7:23 ` Ingo Molnar
2010-07-23 14:26 ` ykzhao
2010-08-17 14:45 ` Jack Steiner
2010-08-17 15:51 ` H. Peter Anvin
2010-08-17 14:42 ` Jack Steiner
2010-08-17 14:39 ` Jack Steiner
2010-07-24 0:14 ` Henrique de Moraes Holschuh
2010-07-24 0:45 ` Matthew Garrett
2010-07-24 12:26 ` Henrique de Moraes Holschuh
2010-08-17 14:49 ` Jack Steiner
2010-08-17 16:02 ` Linus Torvalds
2010-08-24 21:39 ` H. Peter Anvin
2010-08-26 17:17 ` [RFC - V2] " Jack Steiner
2010-08-26 18:08 ` H. Peter Anvin [this message]
2010-12-08 21:22 ` Jack Steiner
2010-12-09 1:27 ` H. Peter Anvin
2010-12-09 3:50 ` Jack Steiner
2010-12-09 6:12 ` Len Brown
2010-08-17 15:59 ` [RFC] " Jack Steiner
2010-08-26 17:47 ` Len Brown
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=4C76AD82.2030105@zytor.com \
--to=hpa@zytor.com \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).