linux-kernel - Re: [PATCH] ACPI: use ioremap

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]

Date:	Mon, 27 Dec 2010 19:35:27 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Shaohua Li <shaohua.li@...el.com>
CC:	Len Brown <lenb@...nel.org>, Jack Steiner <steiner@....com>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	"tony.luck@...il.com" <tony.luck@...il.com>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"gbeshers@....com" <gbeshers@....com>
Subject: Re: [PATCH] ACPI: use ioremap_cache()

On 12/27/2010 07:21 PM, Shaohua Li wrote:
> RCRB is a memory mapped io. In ICH, it's chipset configuration
> registers. this range can't be cached.
> I thought we should add a check like
> if page is E820_RAM or E820_ACPI then
> 	cached_map
> else
> 	uncached_map
> we have page_is_ram() API which just checks E820_RAM, I thought we can
> add a new API to check E820_ACPI.

For x86, that is handled by the MTRRs; for ia64, I would assume
ioremap() handles that somehow, otherwise it wouldn't be able to handle
existing drivers with ioremap() in them.

	-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/