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: <1293512540.10593.46.camel@sli10-conroe>
Date:	Tue, 28 Dec 2010 13:02:20 +0800
From:	Shaohua Li <shaohua.li@...el.com>
To:	"H. Peter Anvin" <hpa@...or.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 Tue, 2010-12-28 at 11:35 +0800, H. Peter Anvin wrote:
> 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; 
does it cause any problem if the pat and mtrr doesn't match?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ