linux-kernel - Re: [PATCH] arm64: support ACPI tables outside of kernel RAM

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:	Fri, 22 May 2015 13:53:46 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Mark Salter <msalter@...hat.com>
Cc:	Matt Fleming <matt.fleming@...el.com>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	Will Deacon <will.deacon@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Hanjun Guo <hanjun.guo@...aro.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: support ACPI tables outside of kernel RAM

On Fri, May 22, 2015 at 08:46:02AM -0400, Mark Salter wrote:
> On Fri, 2015-05-22 at 11:34 +0100, Catalin Marinas wrote:
> > OK, so my preferred options, in this order:
> > 
> > 1. Change the core ACPI kernel code to distinguish between mapping I/O
> >    or RAM (could be as simple as acpi_map not using acpi_os_ioremap but
> >    another API). I guess the code knows when it plans to map tables or
> >    I/O registers
> > 
> > 2. If the above is not possible, add the extra checks as per Mark's
> >    patch but I would rather call this resource "UEFI RAM" than "ACPI",
> >    it's not really ACPI specific.
> 
> Actually, it is ACPI specific. The patch only registers resources for
> EfiACPIReclaimMemory and EfiACPIMemoryNVS regions which are also
> marked as cacheable. On x86 these show up in /proc/iomem as
> "ACPI Tables" and "ACPI Non-volatile Storage". I used "ACPI RAM" to
> avoid having to search for two strings.

My point is more about UEFI describing the entire RAM while the kernel
command line restricts it via "mem=". In this case, the "System RAM"
resources is reduced as well but it does not necessarily mean that the
rest of the RAM is only used by ACPI.

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