linux-kernel - Re: [PATCH] - Mapping ACPI tables as CACHED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D085D79.4010308@zytor.com>
Date:	Tue, 14 Dec 2010 22:17:29 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Len Brown <lenb@...nel.org>
CC:	Jack Steiner <steiner@....com>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	tony.luck@...il.com, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, gbeshers@....com
Subject: Re: [PATCH] - Mapping ACPI tables as CACHED

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/