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: <20101215024136.GB19601@sgi.com>
Date:	Tue, 14 Dec 2010 20:41:36 -0600
From:	Jack Steiner <steiner@....com>
To:	Len Brown <lenb@...nel.org>
Cc:	hpa@...or.com, 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 Tue, Dec 14, 2010 at 07:04:13PM -0500, Len Brown wrote:
> hmm, my arrandale laptop fails to get into graphics mode w/ this patch 
> applied -- last thing i see is the kernel freeing memory, then black 
> screen.
> 
> thanks,
> Len Brown, Intel Open Source Technology Center

Do you know where the ACPI tables actually reside? In RAM
or in another type of memory.

The original version of this patch made the cacheable mapping
a platform attribute that was set via a function called thru
the x86_platform_ops.  This was intended to minimize the potential
for breaking systems with BIOSes that used non-RAM ACPI tables.
There are a lot of different BIOSes and I'm not even close to
understanding them all.

Wonder if I should resurrect that version of the patch....
--
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/